g
space below 256 bytes"). That is why a special feature flag is needed.
Introduce KVM_FEATURE_PCI_GO_MMCONFIG, which can be enabled when the
configuration is known to be safe (e.g. in QEMU).
Signed-off-by: Julia Suvorova
---
Documentation/virt/kvm/cpuid.rst | 4
arch/x86/incl
On Fri, Jul 31, 2020 at 11:22 AM Vitaly Kuznetsov wrote:
>
> Andy Shevchenko writes:
>
> > On Thu, Jul 30, 2020 at 10:37 PM Julia Suvorova wrote:
> >>
> >> Using MMCONFIG instead of I/O ports cuts the number of config space
> >> accesses in half, whi
On Wed, Jul 22, 2020 at 11:43 AM Vitaly Kuznetsov wrote:
>
> Julia Suvorova writes:
>
> > Scanning for PCI devices at boot takes a long time for KVM guests. It
> > can be reduced if KVM will handle all configuration space accesses for
> > non-existent devices without
On Thu, Jul 23, 2020 at 1:19 AM Bjorn Helgaas wrote:
>
> On Wed, Jul 22, 2020 at 02:15:13AM +0200, Julia Suvorova wrote:
> > Scanning for PCI devices at boot takes a long time for KVM guests. It
> > can be reduced if KVM will handle all configuration space accesses for
> &
raw_pci_ops for 64-bit KVM
guests making MMCONFIG the default access method.
[1] https://lkml.org/lkml/2020/5/14/936
Signed-off-by: Julia Suvorova
---
arch/x86/pci/direct.c | 5 +
arch/x86/pci/mmconfig_64.c | 3 +++
2 files changed, 8 insertions(+)
diff --git a/arch/x86/pci/direct.c b/arch
5 matches
Mail list logo