ping
On Tue, Jan 31, 2023 at 2:30 PM wlfightup wrote:
>
> When vfio-pci devices are attached to the downstream, pcie acs
> capability may be needed, Consistent with physical machine.
>
> It has been tested in our environment, and pcie acs capability
> is required in some scenarios.
>
> Claim ACS
The upstream and downstream of the physical machine also have acs capability.
The virtual machine should at least have a way to see the acs
On Sun, Jan 1, 2023 at 5:03 PM Paul Schlacter wrote:
>
> Please help review and merge the code into the master. Thank you very much.
>
> pin
Please help review and merge the code into the master. Thank you very much.
ping
On Sat, Aug 20, 2022 at 7:31 AM Paul Schlacter wrote:
>
> ping
>
> On Thu, Aug 18, 2022 at 10:25 PM Paul Schlacter wrote:
> >
> > If it is a pcie device, check that all devices on the pat
ping
On Thu, Aug 18, 2022 at 10:25 PM Paul Schlacter wrote:
>
> If it is a pcie device, check that all devices on the path from
> the device to the root complex have ACS enabled, and then the
> device will become an iommu_group.
>
> pci_acs_path_enabled, this function in th
If it is a pcie device, check that all devices on the path from
the device to the root complex have ACS enabled, and then the
device will become an iommu_group.
pci_acs_path_enabled, this function in the Linux kernel, it means
that if the device is a PCIe device, check the path from the
device to
On Tue, Aug 16, 2022 at 6:11 PM Michael S. Tsirkin wrote:
>
> On Tue, Aug 16, 2022 at 05:16:38PM +0800, Paul Schlacter wrote:
> > v1 -> v2:
> > - Allow ACS to be disabled.
> > - Suggested by Michael S. Tsirkin, use disable-acs to set property.
> >
> > v1:
v2 -> v3:
- Add the missing code in V2.
v1 -> v2:
- Allow ACS to be disabled.
- Suggested by Michael S. Tsirkin, use disable-acs to set property.
v1:
- Add ACS (Access Control Services) capability.
If it is a pcie device, check that all devices on the path from
the device to the root complex ha
v1 -> v2:
- Allow ACS to be disabled.
- Suggested by Michael S. Tsirkin, use disable-acs to set property.
v1:
- Add ACS (Access Control Services) capability.
If it is a pcie device, check that all devices on the path from
the device to the root complex have ACS enabled, and then the
device will
What's wrong with not disabling the old version?
On Sun, Aug 14, 2022 at 6:48 PM Michael S. Tsirkin wrote:
> On Sun, Aug 14, 2022 at 03:47:49PM +0800, Paul Schlacter wrote:
> > If it is a pcie device, check that all devices on the path from
> >
> > the device to
If it is a pcie device, check that all devices on the path from
the device to the root complex have ACS enabled, and then the
device will become an iommu_group.
it will have the effect of isolation
Signed-off-by: wlfightup
---
hw/pci-bridge/xio3130_upstream.c | 3 +++
1 file changed, 3 in
pin
On Mon, May 16, 2022 at 9:54 PM Wang,Liang(ACG CCN01)
wrote:
> When vfio-pci devices are attached to the downstream, pcie acs
>
> capability may be needed, Consistent with physical machine.
>
>
> It has been tested in our environment, and pcie acs capability
>
> is required in some scenarios
ormal is cache = writeback io significantly higher than none mode
why?
On Wed, Nov 1, 2017 at 8:03 PM, Paul Schlacter wrote:
> Hi David:
> yes, with the same qemu, centos 7.2 guest cache is writeback and
> none, the disk io almost, writeback feeling no effect.
> but 7
Hi David:
yes, with the same qemu, centos 7.2 guest cache is writeback and
none, the disk io almost, writeback feeling no effect.
but 7.1/7.3/7.4 cache is writeback was significantly faster than
none model
On Wed, Nov 1, 2017 at 8:02 PM, Paul Schlacter wrote:
> Hi David:
>
qemu version: 2.9.0
image: centos 7.2 1511 raw
cache mode: writeback
In centos7.2 time, the use of writeback and none, the result of dd disk is
the same io, no change
But I replaced centos7.1 centos7.3 centos7.4 when writeback was
significantly faster than none
Would like to ask what is going
qemu-kvm: -device
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1:
Property '.x-data-plane' not found
What is wrong with this report? is Compiler qemu lost parameters?
report error:
intel_rapl: no valid rapl domains found in package 0
intel_rapl: no valid rapl domains found in package 0
and then will shutdown after in a moment of time
qemu log :
qemu: qemu_mutex_lock: Invalid argument
2017-10-09 09:27:34.781+: shutting down, reason=crashed
Find a sol
this is my stackoverflow question:
https://stackoverflow.com/questions/46219552/host-doesnt-support-requested-feature-cpuid-01hedx-ds-bit-21-does-this-warn
I found a lot of warning from the VM qemu log, Does this warn affect
virtual machine performance or use? , is my libvirt.xml file problem? Or
Like CPU and ram have a maximum value. If I want to produce this product,
provided to the cloud host users. The maximum value is set to how much
more appropriate.
If the settings are too small, users want to dynamically add CPU or memory,
and can't meet the needs of users.
If the setting is to
I made the default config build the qemu-kvm , But I used virsh xml
corresponding machine-type inconsistent, resulting in an error.
error:
2017-09-06T12:16:36.036200Z qemu-kvm: -machine
pc-i440fx-rhel7.0.0,accel=kvm,usb=off: unsupported machine type
Use -machine help to list supported machines
I
19 matches
Mail list logo
