From: Blue Swirl <blauwirbel@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] vhost: fix features ack
Date: Wed, 31 Mar 2010 23:03:05 +0300 [thread overview]
Message-ID: <x2of43fc5581003311303zfbb949f5s5dd2117011a87300@mail.gmail.com> (raw)
In-Reply-To: <4BB3A5A3.7000106@codemonkey.ws>
On 3/31/10, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 03/31/2010 02:38 PM, Blue Swirl wrote:
>
> > On 3/31/10, Michael S. Tsirkin<mst@redhat.com> wrote:
> >
> >
> > > On Wed, Mar 31, 2010 at 03:38:05PM -0300, Luiz Capitulino wrote:
> > > > On Wed, 31 Mar 2010 13:26:23 -0500
> > > > Anthony Liguori<anthony@codemonkey.ws> wrote:
> > > >
> > > > > On 03/31/2010 01:20 PM, Michael S. Tsirkin wrote:
> > > > > > From: David L Stevens<dlstevens@us.ibm.com>
> > > > > >
> > > > > > vhost driver in qemu didn't ack features, and this happens
> > > > > > to work because we don't really require any features. However,
> > > > > > it's better not to rely on this. This patch passes features to
> > > > > > vhost as guest acks them.
> > > > > >
> > > > > > Signed-off-by: David L Stevens<dlstevens@us.ibm.com>
> > > > > > Signed-off-by: Michael S. Tsirkin<mst@redhat.com>
> > > > > > ---
> > > > > >
> > > > > > Anthony, here's a fixup patch to address an issue in vhost
> > > > > > patches. Incidentially, what's the status of the vhost
> patchset?
> > > > > >
> > > > >
> > > > >
> http://repo.or.cz/w/qemu/aliguori-queue.git
> vhost
> > > > >
> > > > > Is what I'm currently testing. With vhost disabled, the
> following seg
> > > > > faults:
> > > > >
> > > > > qemu-system-x86_64 -hda ~/images/linux.img -net tap -net
> > > > > nic,model=virtio -enable-kvm
> > > > >
> > > > > But not when using TCG. I'm not sure that it's your patches at
> fault
> > > > > and I'm attempting to bisect now to figure that out.
> > > >
> > > > Probably this is the same segfault I'm getting right now in master,
> > > > bisect says it's:
> > > >
> > > > """
> > > > commit ad96090a01d848df67d70c5259ed8aa321fa8716
> > > > Author: Blue Swirl<blauwirbel@gmail.com>
> > > > Date: Mon Mar 29 19:23:52 2010 +0000
> > > >
> > > > Refactor target specific handling, compile vl.c only once
> > > > """
> > >
> > > Why are the compile once patches helpful? They seem to introduce
> > > churn and bugs, they actively make it harder to extend qemu as you
> can't use
> > > target-specific code in code that is compiled once, they might have
> > > performance penalty - and what do we gain? Any given user is unlikely
> to
> > > need to build on more than one target, distros have enough computing
> > > power to build in parallel.
> > >
> > >
> > As has been explained many times, knowledge about CPU
> specific
> > features has no place in devices. Actively removing CPU specifics from
> > devices is good but preventing new bad code to be committed is better.
> >
> > I don't have distro computing powers (unless some distro's compute
> > center only has two low power machines) and I guess some other
> > developers don't have either. All developers and patch submitters are
> > expected to compile all targets. This patch set has decreased the
> > number of files compiled by about 20%.
> >
> >
>
> BTW, this seems to do it. I'll commit after some testing.
But this makes kvm_enabled() check dynamic and code that was
eliminated by compiler for !CONFIG_KVM will now be generated.
Wouldn't adding CONFIG_KVM to config-host.h also solve the problem?
next prev parent reply other threads:[~2010-03-31 20:03 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
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 [this message]
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=x2of43fc5581003311303zfbb949f5s5dd2117011a87300@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=anthony@codemonkey.ws \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).