qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Xen-devel] [PATCH] libxl: Remove qxl support for the 4


From: Fabio Fantoni
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] libxl: Remove qxl support for the 4.3 release
Date: Wed, 18 Sep 2013 17:26:14 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8

Il 18/09/2013 16:30, Jan Beulich ha scritto:
On 18.09.13 at 16:12, Fabio Fantoni <address@hidden> wrote:
Il 18/09/2013 14:42, Jan Beulich ha scritto:
On 18.09.13 at 14:29, Fabio Fantoni <address@hidden> wrote:
I not see the MMIO error on logs, what must I do to see it or any
similar debug information?
Tell me if I must do other specific test or you need other details.
Without the patch you ought to have seen "bad mmio size ..."
I was unable to see the MMIO error on each log files also before the patch.
I don't know if I have enable sufficent debug to log them.
And I have no ideaon how to do it.
This is a guest warning (from log level perspective), so by default
would be visible in a rate limited fashion. If you want to be certain,
just add "loglvl=all guest_loglvl=all". But I'm more and more
convinced that the information we got from you originally was
misleading.

On grub.cfg now I have:
...
multiboot /boot/xen.gz placeholder dom0_mem=4G,max:4G loglvl=all guest_loglvl=all
...
But I'm unable to see debug related information in log files.
This was the test of Anthony Perard with all details about the problem:
http://lists.xen.org/archives/html/xen-devel/2013-05/msg02050.html

So my questions are:
- Is your patch aimed to completely solve cpus instrictions with MMIO operands > 8 byte or
- does it need also some qemu changes?
I also added qemu-devel and anthony perard on cc.
Thanks for any reply.



Is there another method to test effettive working of SSE >=2 istructions?
You realize that we're not talking about arbitrary SSE instructions,
but only such with their memory operand being in MMIO space.
Anything else doesn't hit the emulator.
Jan





reply via email to

[Prev in Thread] Current Thread [Next in Thread]