Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-10 Thread Roger Pau Monné
On Tue, Jun 10, 2025 at 05:45:52PM +0200, Jan Beulich wrote: > On 05.06.2025 18:16, Roger Pau Monne wrote: > > @@ -271,6 +279,43 @@ void pci_setup(void) > > if ( bar_sz == 0 ) > > continue; > > > > +if ( !xenpci_bar_uc && > > + ((bar_data

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-10 Thread Jan Beulich
On 05.06.2025 18:16, Roger Pau Monne wrote: > @@ -271,6 +279,43 @@ void pci_setup(void) > if ( bar_sz == 0 ) > continue; > > +if ( !xenpci_bar_uc && > + ((bar_data & PCI_BASE_ADDRESS_SPACE) == > + PCI_BASE_ADDRESS_SPACE_M

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-09 Thread Oleksii Kurochko
On 6/6/25 3:41 PM, Roger Pau Monné wrote: On Thu, Jun 05, 2025 at 06:16:59PM +0200, Roger Pau Monne wrote: The Xen PCI device (vendor ID 0x5853) exposed to x86 HVM guests doesn't have the functionality of a traditional PCI device. The exposed MMIO BAR is used by some guests (including Linux) a

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-06 Thread Roger Pau Monné
On Fri, Jun 06, 2025 at 01:00:19PM +, Tu Dinh wrote: > Hi Roger, > > On 05/06/2025 18:20, Roger Pau Monne wrote: > > The Xen PCI device (vendor ID 0x5853) exposed to x86 HVM guests doesn't > > have the functionality of a traditional PCI device. The exposed MMIO BAR > > is used by some guests

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-06 Thread Roger Pau Monné
On Thu, Jun 05, 2025 at 06:16:59PM +0200, Roger Pau Monne wrote: > The Xen PCI device (vendor ID 0x5853) exposed to x86 HVM guests doesn't > have the functionality of a traditional PCI device. The exposed MMIO BAR > is used by some guests (including Linux) as a safe place to map foreign > memory,

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-06 Thread Tu Dinh
On 06/06/2025 15:23, Roger Pau Monné wrote: [...] >> >> Since this is meant to be a workaround, I wonder if it makes more sense >> to flip the setting (`xenpci_bar_wb`) and make it 0 by default? > > I originally didn't want to go that route, because while it's true > that the default MTRR type is s

Re: [PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-06 Thread Tu Dinh
Hi Roger, On 05/06/2025 18:20, Roger Pau Monne wrote: > The Xen PCI device (vendor ID 0x5853) exposed to x86 HVM guests doesn't > have the functionality of a traditional PCI device. The exposed MMIO BAR > is used by some guests (including Linux) as a safe place to map foreign > memory, including

[PATCH v3] x86/hvmloader: select xenpci MMIO BAR UC or WB MTRR cache attribute

2025-06-05 Thread Roger Pau Monne
The Xen PCI device (vendor ID 0x5853) exposed to x86 HVM guests doesn't have the functionality of a traditional PCI device. The exposed MMIO BAR is used by some guests (including Linux) as a safe place to map foreign memory, including the grant table itself. Traditionally BARs from devices have t