[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH V2 20/23] xen/ioreq: Make x86's send_invalidate_req() common
On 12.11.20 13:55, Jan Beulich wrote: Hi Jan On 15.10.2020 18:44, Oleksandr Tyshchenko wrote:--- a/xen/include/asm-x86/hvm/io.h +++ b/xen/include/asm-x86/hvm/io.h @@ -97,7 +97,6 @@ bool relocate_portio_handler( unsigned int size);void send_timeoffset_req(unsigned long timeoff);-void send_invalidate_req(void); bool handle_mmio_with_translation(unsigned long gla, unsigned long gpfn, struct npfec); bool handle_pio(uint16_t port, unsigned int size, int dir); diff --git a/xen/include/xen/ioreq.h b/xen/include/xen/ioreq.h index 0679fef..aad682f 100644 --- a/xen/include/xen/ioreq.h +++ b/xen/include/xen/ioreq.h @@ -126,6 +126,7 @@ struct ioreq_server *select_ioreq_server(struct domain *d, int send_ioreq(struct ioreq_server *s, ioreq_t *proto_p, bool buffered); unsigned int broadcast_ioreq(ioreq_t *p, bool buffered); +void send_invalidate_ioreq(void);Again while renaming this function anyway could we see about giving it a suitable and consistent name? Maybe ioreq_request_mapcache_invalidate() or (to avoid the double "request") ioreq_signal_mapcache_invalidate()? Maybe even ioreq_server_...(). iirc send_invalidate_ioreq() was one of the proposed names during V1 review. But to follow new scheme, I am fine with both the first and second. -- Regards, Oleksandr Tyshchenko
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |