于Mon 12 Sep 2011 03:59:07 PM CST,Kevin Wolf写到:
Am 10.09.2011 02:54, schrieb Dong Xu Wang:
于Fri 09 Sep 2011 10:27:26 PM CST,Kevin Wolf写到:
Am 09.09.2011 07:48, schrieb Dong Xu Wang:
As raw file format does not support backing_file and copy on write feature, so
I add COW to it to support backing_
m?
>
>
> Thank you
>
--
Regards,
Donald Wang
I've just this week begun using qemu (actually qemu-kvm) on a 64-bit
Slackware (13.37) system. You people have produced a very useful piece of
software, very nice work. But I must say that the documentation does not do
the software justice. I have just spent a maddening several hours trying to
get
Need to check that guest slot/device number is not > 31 or walk off
the devfn table when checking if a devfn is available or not in a guest.
before this fix, passing in an addr=abc or addr=34,
can crash qemu, sometimes fail gracefully if data past end
of devfn table fails the availability test.
his, why? won't this cause problems like redundant
interrupts? any special consideration about this?
donald
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
i see. you are right, thanks very much2006/10/8, Paul Brook <[EMAIL PROTECTED]>:
On Saturday 07 October 2006 19:15, Donald Liew wrote:> i'm reading qemu-system-arm code and trying to add some more> evaluation boards support for it. in the 0.8.2 source code i found> somethin
ot;);
if (vms->dtb_randomness) {
+1 to Peter's suggested comment, otherwise, unless privy to this thread,
one would wonder how/why.
Reviewed-by: Donald Dutile
On 11/7/24 3:31 PM, Nicolin Chen wrote:
Hi Eric,
On Thu, Nov 07, 2024 at 12:11:05PM +0100, Eric Auger wrote:
On 11/1/24 05:09, Nicolin Chen wrote:
Hi,
This is a continued discussion following previous month's:
https://lore.kernel.org/qemu-devel/Zvr%2Fbf7KgLN1cjOl@Asurada-Nvidia/
Kernel ch
On 11/27/24 11:00 AM, Jason Gunthorpe wrote:
On Wed, Nov 27, 2024 at 10:21:24AM +, Shameerali Kolothum Thodi wrote:
For SMMUv3, NVIDIA-specific vCMDQ, it needs a parameter to state that
specifically,
since I'm concluding from reading the SMMUv3 version G.a spec, that
ECMDQ was added
to be
On 11/27/24 5:21 AM, Shameerali Kolothum Thodi wrote:
-Original Message-
From: Donald Dutile
Sent: Tuesday, November 26, 2024 6:29 PM
To: Nicolin Chen ; Eric Auger
Cc: Shameerali Kolothum Thodi
; qemu-...@nongnu.org;
qemu-devel@nongnu.org; peter.mayd...@linaro.org; j
On 11/13/24 1:05 PM, Nicolin Chen wrote:
Hi Eric,
On Wed, Nov 13, 2024 at 06:12:15PM +0100, Eric Auger wrote:
On 11/8/24 13:52, Shameer Kolothum wrote:
@@ -181,6 +181,7 @@ static const MemMapEntry base_memmap[] = {
[VIRT_PVTIME] = { 0x090a, 0x0001 },
[VIRT_SE
On 11/28/24 7:54 AM, Jason Gunthorpe wrote:
On Wed, Nov 27, 2024 at 08:44:47PM -0800, Nicolin Chen wrote:
On Wed, Nov 27, 2024 at 11:29:06PM -0500, Donald Dutile wrote:
On 11/27/24 5:21 AM, Shameerali Kolothum Thodi wrote:
W.r.t naming, maybe something related to "hardware-accele
On 12/13/24 8:19 AM, Daniel P. Berrangé wrote:
On Fri, Dec 13, 2024 at 08:46:42AM -0400, Jason Gunthorpe wrote:
On Fri, Dec 13, 2024 at 12:00:43PM +, Daniel P. Berrangé wrote:
On Fri, Nov 08, 2024 at 12:52:37PM +, Shameer Kolothum via wrote:
Hi,
This series adds initial support for
Nicolin,
Hi!
On 1/8/25 11:45 PM, Nicolin Chen wrote:
On Mon, Dec 16, 2024 at 10:01:29AM +, Shameerali Kolothum Thodi wrote:
And patches prior to this commit adds that support:
4ccdbe3: ("cover-letter: Add HW accelerated nesting support for arm
SMMUv3")
Nicolin is soon going to send out th
Hi Suravee!
Not your issue, but wondering if others know:
Why isn't this an issue for Intel-vtd-iommu & ARM-SMMUV3 ?
Are they instantiated as non-PCI-id (platform) devices, but AMD puts their
IOMMU in PCI space?
Adv. thanks for the info.
- Don
On 3/4/25 1:37 PM, Suravee Suthikulpanit wrote:
On 3/4/25 9:56 PM, Suthikulpanit, Suravee wrote:
On 3/5/2025 6:02 AM, Donald Dutile wrote:
Hi Suravee!
Not your issue, but wondering if others know:
Why isn't this an issue for Intel-vtd-iommu & ARM-SMMUV3 ?
Are they instantiated as non-PCI-id (platform) devices, but AMD p
Shameer,
Hey,
On 3/11/25 10:10 AM, Shameer Kolothum wrote:
From: Nicolin Chen
Read the underlying SMMUv3 device info and set corresponding IDR
bits. We need at least one cold-plugged vfio-pci dev associated
with the smmuv3-accel instance to do this now. Hence fail if it
is not available.
T
On 3/11/25 10:10 AM, Shameer Kolothum wrote:
From: Nicolin Chen
If a vSMMU is configured as a accelerated one, HW IOTLB will be used
and all cache invalidation should be done to the HW IOTLB too, v.s.
the emulated iotlb. In this case, an iommu notifier isn't registered,
as the devices behind
Shameer,
Hi,
On 3/11/25 10:10 AM, Shameer Kolothum wrote:
From: Nicolin Chen
Inroduce an SMMUCommandBatch and some helpers to batch and issue the
Introduce
commands. Currently separate out TLBI commands and device cache commands
to avoid some errata on certain versions of SMMUs
Shameer,
Hi,
On 3/11/25 10:10 AM, Shameer Kolothum wrote:
From: Nicolin Chen
Allocate and associate a vDEVICE object for the Guest device
with the vIOMMU. This will help the kernel to do the
vSID --> sid translation whenever required (eg: device specific
invalidations).
Signed-off-by: Nicoli
Doesn't this commit become moot, if accel becomes an smmuv3 option vs separate
device object altogether,
dynamically added if a pdev is attached to a host SMMUv3 that has accel
feature(s)?
Blocking w/virtio-iommu falls under the same situation mentioned in 03/20 wrt
mixing emulated & physica
On 3/19/25 5:26 AM, Shameerali Kolothum Thodi wrote:
Hi Don,
Hey!
-Original Message-
From: Donald Dutile
Sent: Tuesday, March 18, 2025 10:12 PM
To: Shameerali Kolothum Thodi
; qemu-...@nongnu.org;
qemu-devel@nongnu.org
Cc: eric.au...@redhat.com; peter.mayd...@linaro.org; j
On 3/19/25 5:48 AM, Shameerali Kolothum Thodi wrote:
-Original Message-
From: Donald Dutile
Sent: Wednesday, March 19, 2025 1:31 AM
To: Shameerali Kolothum Thodi
; qemu-...@nongnu.org;
qemu-devel@nongnu.org
Cc: eric.au...@redhat.com; peter.mayd...@linaro.org; j...@nvidia.com
On 3/18/25 3:13 PM, Nicolin Chen wrote:
On Tue, Mar 18, 2025 at 07:31:36PM +0100, Eric Auger wrote:
On 3/17/25 9:19 PM, Nicolin Chen wrote:
On Mon, Mar 17, 2025 at 04:24:53PM -0300, Jason Gunthorpe wrote:
On Mon, Mar 17, 2025 at 12:10:19PM -0700, Nicolin Chen wrote:
Another question: how d
On 3/17/25 3:24 PM, Jason Gunthorpe wrote:
On Mon, Mar 17, 2025 at 12:10:19PM -0700, Nicolin Chen wrote:
Another question: how does an emulated device work with a vSMMUv3?
I could imagine that all the accel steps would be bypassed since
!sdev->idev. Yet, the emulated iotlb should cache its tr
Shameer,
Hi!
On 3/11/25 10:10 AM, Shameer Kolothum wrote:
User must associate a pxb-pcie root bus to smmuv3-accel
and that is set as the primary-bus for the smmu dev.
Signed-off-by: Shameer Kolothum
---
hw/arm/smmuv3-accel.c | 19 +++
1 file changed, 19 insertions(+)
diff
Jason,
Hey!
On 3/18/25 8:23 PM, Jason Gunthorpe wrote:
On Tue, Mar 18, 2025 at 05:22:51PM -0400, Donald Dutile wrote:
I agree with Eric that 'accel' isn't needed -- this should be
ascertained from the pSMMU that a physical device is attached to.
I seem to remember the point w
On 3/19/25 2:09 PM, Eric Auger wrote:
Hi Nicolin,
On 3/19/25 6:14 PM, Nicolin Chen wrote:
On Wed, Mar 19, 2025 at 05:45:51PM +0100, Eric Auger wrote:
On 3/17/25 8:10 PM, Nicolin Chen wrote:
On Mon, Mar 17, 2025 at 07:07:52PM +0100, Eric Auger wrote:
On 3/17/25 6:54 PM, Nicolin Chen wro
On 3/19/25 1:04 PM, Eric Auger wrote:
On 3/18/25 10:22 PM, Donald Dutile wrote:
On 3/18/25 3:13 PM, Nicolin Chen wrote:
On Tue, Mar 18, 2025 at 07:31:36PM +0100, Eric Auger wrote:
On 3/17/25 9:19 PM, Nicolin Chen wrote:
On Mon, Mar 17, 2025 at 04:24:53PM -0300, Jason Gunthorpe wrote
On 3/19/25 2:21 PM, Eric Auger wrote:
Hi Don,
On 3/19/25 5:21 PM, Donald Dutile wrote:
On 3/19/25 5:26 AM, Shameerali Kolothum Thodi wrote:
Hi Don,
Hey!
-Original Message-
From: Donald Dutile
Sent: Tuesday, March 18, 2025 10:12 PM
To: Shameerali Kolothum Thodi
; qemu
On 3/24/25 10:56 AM, Eric Auger wrote:
On 3/21/25 1:59 AM, Donald Dutile wrote:
On 3/19/25 2:21 PM, Eric Auger wrote:
Hi Don,
On 3/19/25 5:21 PM, Donald Dutile wrote:
On 3/19/25 5:26 AM, Shameerali Kolothum Thodi wrote:
Hi Don,
Hey!
-Original Message-
From: Donald
On 3/19/25 1:00 PM, Eric Auger wrote:
Hi,
On 3/19/25 1:23 AM, Jason Gunthorpe wrote:
On Tue, Mar 18, 2025 at 05:22:51PM -0400, Donald Dutile wrote:
I agree with Eric that 'accel' isn't needed -- this should be
ascertained from the pSMMU that a physical device is attached
Zhenzhong,
Hi!
Eric asked me to review this series.
Since it's rather late since you posted will summarize review feedback
below/bottom.
- Don
On 2/19/25 3:22 AM, Zhenzhong Duan wrote:
Hi,
Per Jason Wang's suggestion, iommufd nesting series[1] is split into
"Enable stage-1 translation for em
What is happening with this patch? I would like to use this code.
-Don Slutz
From: qemu-devel-bounces+don=cloudswitch@nongnu.org
[qemu-devel-bounces+don=cloudswitch@nongnu.org] on behalf of Gerd Hoffmann
[kra...@redhat.com]
Sent: Tuesday, May
On 09/25/14 11:07, Dr. David Alan Gilbert wrote:
> * Slutz, Donald Christopher (dsl...@verizon.com) wrote:
>> What is happening with this patch? I would like to use this code.
> I need to rework it for the new machine types code; but it was pretty
> low down my list of priorities
On 09/30/14 06:35, Stefano Stabellini wrote:
> On Mon, 29 Sep 2014, Don Slutz wrote:
>> On 09/29/14 06:25, Stefano Stabellini wrote:
>>> On Mon, 29 Sep 2014, Stefano Stabellini wrote:
On Fri, 26 Sep 2014, Don Slutz wrote:
> This adds synchronisation of the vcpu registers
> between Xen
On 06/17/14 16:17, Michael S. Tsirkin wrote:
> On Tue, Jun 17, 2014 at 04:08:54PM -0400, Konrad Rzeszutek Wilk wrote:
>> On Tue, Jun 17, 2014 at 10:43:29PM +0300, Michael S. Tsirkin wrote:
[snip]
>> I think he mentioned PCI devices, not PCIe.
> OK that's a small niche but it makes some sense.
> So
Do I need to repost with the 2 Reviewed-by ?
-Don Slutz
On 10/06/14 05:26, Richard W.M. Jones wrote:
> On Fri, Oct 03, 2014 at 05:33:37PM -0400, Don Slutz wrote:
>> From: "Dr. David Alan Gilbert"
>>
>> This is a pc & q35 only machine opt.
>>
>> VMWare apparently doesn't like running under QEM
So how the commit message change:
On 06/25/14 16:19, Don Slutz wrote:
> This will prevent correct migration from QEMU 1.7.0 for these
> machine types when -m 3.5G is specified.
This fixes bug:
https://bugs.launchpad.net/qemu/+bug/1334307
> Paolo Bonzini asked that:
>
> smbios_le
On 06/24/14 22:49, Chen, Tiejun wrote:
> On 2014/5/19 19:22, Gerd Hoffmann wrote:
>> Hi,
>>
>>> I think '-vga none' just guarantees the qemu vga cards doesn't occupy
>>> 00:02.0, but this doesn't mean others use this specific slot since in
>>> qemu internal, we always pass -1 to assign a slot aut
If you change the video resolution while running a Windows XP image such that
it uses fewer bytes of VRAM (either by using fewer bytes per pixel or by
lowering the resolution) then some window backgrounds will become corrupted.
This happens because the Windows XP Cirrus Logic driver assumes that VR
E. Reiter
>Sent: Tuesday, May 09, 2006 2:29 PM
>To: qemu-devel@nongnu.org
>Subject: Re: [Qemu-devel] [PATCH]Fix for minor video
>corruption under Windows
>
>Donald...
>
>thanks... I actually posted a patch to fix this sometime ago, but your
>patch seems more thorough and pr
WD-
I see the problem here, `patch' got confused because my patch was
against a 0.8.0 tree and you applied it to a 0.8.1 tree. You wound up
making the change to `cirrus_hook_read_sr', where the Windows driver
attempts to read the mode register. The patch is supposed to apply to
the routine `cirr
ursday, May 11, 2006 4:48 PM
>To: qemu-devel@nongnu.org
>Subject: Re: [Qemu-devel] [PATCH]Fix for minor video
>corruption under Windows
>
>Hi,
>
>I think the proper fix must be done in the BIOS (set VRAM to 0xFF at
>cirrus mode init). I made a patch for that but I must test it
Is anybody working on creating an EHCI driver for the USB subsystem? I
have a need to access high speed devices and wanted to find out if I'd
be re-inventing the wheel before I start on this.
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[EMAIL PROTECTED]
Ph: (303)440-1368
__
Well, calling it worthless is a little harsh. As with all documentation
I'm sure it could be made better but, if you read the documentation
carefully, it actually tells you what to do.
Note that there are instructions on how to boot a CD image (section 3.3
of the user manual, check out the option
We've seen multiple issues with tightVNC, mainly because I don't believe
that tightvnc does resize requests at all. Can you try a realvnc client
and see if you see the same issues?
--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[EMAIL PROTECTED]
Ph: (303)443-3786
>-Origina
While tracking down a problem with getting X to work with the VNC
version of Qemu I discovered a problem in the way the Qemu mouse
emulation was handling mouse reset commands. Turns out, the emulation
code is a little over aggressive in dealing with reset commands for the
mouse. Since there are c
Interesting. You're right, the protocol explicitly says that both
`reset' and `set to default' are supposed to disable the mouse. I have
to admit, I was basing my patch on the fact that, in tracing the
commands I received from the X server, I saw a `reset' that was not
followed by an `enable'. I
Ken,
Lookup starting the gvncviewer tool after you start the virtual machine. To
get the display for the VMs I run gvncviewer and sometimes spicec.
Don
Kenneth Adam Miller wrote on 9/7/24 4:58 PM:
Hello,
I've got qemu built and now I need to figure out how to run it with what I've
got.
Public bug reported:
The output for the "-cpu help" on the Sparc executables is not
generating accurate information.
Running
./qemu-sparc64 -cpu help
produces:
Sparc Fujitsu Sparc64 IU 00040002 FPU MMU NWINS 4
Sparc Fujitsu Sparc64 III IU 00040003 FPU 000
51 matches
Mail list logo
