Re: [PATCH] x86/io-apic: fix directed EOI when using AMd-Vi interrupt remapping

2024-10-21 Thread Woodhouse, David
On Sat, 2024-10-19 at 05:23 +0200, Marek Marczykowski-Górecki wrote: > On Fri, Oct 18, 2024 at 10:08:13AM +0200, Roger Pau Monne wrote: > > When using AMD-VI interrupt remapping the vector field in the IO-APIC RTE is > > repurposed to contain part of the offset into the remapping table.  > > Previ

Re: [RFC PATCH v3 3/5] xen: add option to disable legacy backends

2023-11-27 Thread Woodhouse, David
On Fri, 2023-11-24 at 23:24 +, Volodymyr Babchuk wrote: > This patch makes legacy backends optional. As was discussed at [1] > this is a solution to a problem when we can't run QEMU as a device > model in a non-privileged domain. This is because legacy backends > assume that they are always run

Re: [PATCH v2 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it

2023-11-22 Thread Woodhouse, David
On Wed, 2023-11-22 at 23:49 +, Volodymyr Babchuk wrote: > > I can just pull it from this link, if you don't mind. Please do; thank you! smime.p7s Description: S/MIME cryptographic signature Amazon Development Centre (London) Ltd. Registered in England and Wales with registration number

Re: [PATCH v2 2/6] xen: backends: touch some XenStore nodes only if device...

2023-11-22 Thread Woodhouse, David
On Wed, 2023-11-22 at 17:03 +, Paul Durrant wrote: > > > This patch checks presence of xendev->backend to check if Xen PV > > device is acting as a backend (i.e. it was configured by Xen > > Technally *all* XenDevice objects are backends. Right. The key criterion is whether the backend was c

Re: [PATCH v2 1/6] hw/xen: Set XenBackendInstance in the XenDevice before realizing it

2023-11-22 Thread Woodhouse, David
On Wed, 2023-11-22 at 17:05 +, Paul Durrant wrote: > On 21/11/2023 22:10, Volodymyr Babchuk wrote: > > From: David Woodhouse > > > > This allows a XenDevice implementation to know whether it was created > > by QEMU, or merely discovered in XenStore after the toolstack created > > it. This wil

Re: [PATCH-for-9.0 04/10] hw/xen: Factor xen_arch_align_ioreq_data() out of handle_ioreq()

2023-11-13 Thread Woodhouse, David
On 13 Nov 2023 10:22, Philippe Mathieu-Daudé wrote: Per commit f17068c1c7 ("xen-hvm: reorganize xen-hvm and move common function to xen-hvm-common"), handle_ioreq() is expected to be target-agnostic. However it uses 'target_ulong', which is a target specific definition. In order to compile this

Re: [PATCH] arm/xen: Don't probe xenbus as part of an early initcall

2021-02-10 Thread Woodhouse, David
On Wed, 2021-02-10 at 17:06 +, Julien Grall wrote: > From: Julien Grall > > After Commit 3499ba8198cad ("xen: Fix event channel callback via > INTX/GSI"), xenbus_probe() will be called too early on Arm. This will > recent to a guest hang during boot. > > If there hang wasn't there, we would

Re: [Xen-devel] [PATCH 2/2] domain: use PGC_extra domheap page for shared_info

2020-02-26 Thread Woodhouse, David
On Wed, 2020-02-26 at 16:12 +, Julien Grall wrote: > (+David) > > On 26/02/2020 15:23, Jan Beulich wrote: > > On 26.02.2020 15:05, Durrant, Paul wrote: > > > > From: Jan Beulich > > > > Sent: 26 February 2020 13:58 > > > > > > > > On 25.02.2020 10:53, Paul Durrant wrote: > > > > > There's no

Re: [Xen-devel] [PATCH] xen/x86: domain: Free all the pages associated to struct domain

2020-01-22 Thread Woodhouse, David
On Wed, 2020-01-22 at 13:15 +, Andrew Cooper wrote: > > > I'd much rather see the original patch reverted. The current size of > > > struct domain with lockprofile enabled is 3200 bytes. > > > > Let me have a look first to see when/why struct domain is less than 4K > > with lockprofile. > >

Re: [Xen-devel] [PATCH] evtchn: make support for different ABIs tunable

2019-08-07 Thread Woodhouse, David
On Wed, 2019-08-07 at 12:40 +0100, Andrew Cooper wrote: > On 07/08/2019 12:20, Eslam Elnikety wrote: > > Adding support for FIFO event channel ABI was first introduced in Xen 4.4 > > (see 88910061ec6). Make this support tunable, since the choice of which > > event channel ABI has implications for h

Re: [Xen-devel] Ongoing/future speculative mitigation work

2018-10-22 Thread Woodhouse, David
Adding Stefan to Cc. Should we take this to the spexen or another mailing list? On Mon, 2018-10-22 at 15:55 +0100, Wei Liu wrote: > On Thu, Oct 18, 2018 at 06:46:22PM +0100, Andrew Cooper wrote: > > Hello, > > > > This is an accumulation and summary of various tasks which have been > > discusse

Re: [Xen-devel] [PATCH qemu-xen-traditional] xen/pt: allow QEMU to request MSI unmasking at bind time

2018-07-31 Thread Woodhouse, David
ne 18, 2018 2:43 PM > To: Paraschiv, Andra-Irina > Cc: xen-devel@lists.xenproject.org; sstabell...@kernel.org; jbeulich@ > suse.com; andrew.coop...@citrix.com; Woodhouse, David > Subject: Re: [PATCH qemu-xen-traditional] xen/pt: allow QEMU to > request MSI unmasking at bind time >

Re: [Xen-devel] [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel()

2018-07-11 Thread Woodhouse, David
On Wed, 2018-07-11 at 11:46 +0200, Juergen Gross wrote: > On 11/07/18 11:15, Woodhouse, David wrote: > > > > On Wed, 2018-05-30 at 13:09 +0200, Juergen Gross wrote: > > > > > > There is no need to set the same capabilities for each cpu > > > individu

Re: [Xen-devel] [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel()

2018-07-11 Thread Woodhouse, David
On Wed, 2018-05-30 at 13:09 +0200, Juergen Gross wrote: > There is no need to set the same capabilities for each cpu > individually. This can easily be done for all cpus when starting the > kernel. > > Upstream commit: 0808e80cb760de2733c0527d2090ed2205a1eef8 ("xen: set > cpu capabilities from xen

Re: [Xen-devel] [PATCH] xen: fix pv domain on amd in 4.9 stable branch

2018-05-30 Thread Woodhouse, David
On Wed, 2018-05-30 at 11:46 +0200, Greg KH wrote: > On Wed, May 30, 2018 at 11:33:22AM +0200, Juergen Gross wrote: > > > > On 30/05/18 10:33, Greg KH wrote: > > > > > > On Tue, May 29, 2018 at 03:11:36PM +0200, Juergen Gross wrote: > > > > > > > > Commit 944e0fc51a89c9827b98813d65dc083274777c7f

Re: [Xen-devel] [PATCH v10 09/11] x86/ctxt: Issue a speculation barrier between vcpu contexts

2018-01-24 Thread Woodhouse, David
On Wed, 2018-01-24 at 13:12 +, Andrew Cooper wrote: > + * Squash the domid and vcpu id together for comparason *comparison > + * efficiency.  We could in principle stash and compare the > struct > + * vcpu pointer, but this risks a false alias if a domain