From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] vhost: fix features ack
Date: Thu, 01 Apr 2010 11:08:35 -0500 [thread overview]
Message-ID: <4BB4C503.1060400@codemonkey.ws> (raw)
In-Reply-To: <k2gf43fc5581004010854w9cc4624azde071378580a1db9@mail.gmail.com>
On 04/01/2010 10:54 AM, Blue Swirl wrote:
> On 4/1/10, Anthony Liguori<anthony@codemonkey.ws> wrote:
>
>> On 03/31/2010 05:45 PM, Aurelien Jarno wrote:
>>
>>
>>> While it probably make sense to achieve this goal, it doesn't mean it
>>> should be done the dirty way.
>>>
>>> For example it is known for a lot of time that the solution for the
>>> bswap in the device code is to add a bus model doing the byteswapping.
>>> Removing the #ifdef by deciding "this device will only be big/little
>>> endian" doesn't seem to go in the right direction.
>>>
>>>
>>>
>> Yeah, I'm having real trouble with the KVM regression. I thought I had it
>> fixed but linux-user really made a mess of things. There's no simple
>> solution that doesn't require quite a bit of refactoring which I'd rather do
>> in a less ugly way. We've already been discussing getting rid of all the
>> kvm_enabled() stuff and I think doing that properly is going to be needed to
>> handle this correctly.
>>
> Strange, does linux-user use kvm.h (indirectly)?
>
Yes, because various things in target-i386 use kvm.h.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-04-01 16:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 18:20 [Qemu-devel] [PATCH] vhost: fix features ack Michael S. Tsirkin
2010-03-31 18:26 ` [Qemu-devel] " Anthony Liguori
2010-03-31 18:38 ` Luiz Capitulino
2010-03-31 19:07 ` Michael S. Tsirkin
2010-03-31 19:24 ` Anthony Liguori
2010-03-31 19:25 ` Michael S. Tsirkin
2010-03-31 19:37 ` Anthony Liguori
2010-03-31 19:54 ` Blue Swirl
2010-03-31 19:55 ` Anthony Liguori
2010-03-31 20:06 ` Nathan Froyd
2010-03-31 19:46 ` Blue Swirl
2010-03-31 22:45 ` Aurelien Jarno
2010-04-01 2:45 ` Anthony Liguori
2010-04-01 2:46 ` Anthony Liguori
2010-04-01 15:54 ` Blue Swirl
2010-04-01 16:08 ` Anthony Liguori [this message]
2010-04-01 16:08 ` Blue Swirl
2010-03-31 19:38 ` Blue Swirl
2010-03-31 19:42 ` Anthony Liguori
2010-03-31 20:03 ` Blue Swirl
2010-04-01 12:09 ` Paul Brook
2010-04-01 14:53 ` Michael S. Tsirkin
2010-04-04 12:14 ` Michael S. Tsirkin
2010-04-13 21:58 ` [Qemu-devel] " Aurelien Jarno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB4C503.1060400@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.