All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Hollis Blanchard <hollis_blanchard@mentor.com>,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] vhost_net.c broken by --kerneldir
Date: Thu, 26 Aug 2010 18:21:42 +0300	[thread overview]
Message-ID: <20100826152142.GV10499@redhat.com> (raw)
In-Reply-To: <201008261715.36022.arnd@arndb.de>

On Thu, Aug 26, 2010 at 05:15:35PM +0200, Arnd Bergmann wrote:
> On Wednesday 25 August 2010, Hollis Blanchard wrote:
> > > We only recently fixed the kernel to have this warning in types.h, which
> > > triggers more often than kernel.h, where it used to be before. In 2.6.35
> > > and before, you consequently would not have noticed the problem.
> > >    
> > 
> > Thanks Arnd, that explains it.
> > 
> > It looks like the --kerneldir option needs to be re-thought.
> 
> Yes. I believe that we should just kill that option, since there is
> no reason for building with set of headers from a different kernel
> than the one your glibc normally uses.
> 
> You obviously need copies of some headers to match qemu code, e.g.
> the kvm headers, but for those we have run-time compatibility code
> in qemu. Building with a newer kernel header is pointless because
> qemu would not use any of the features that were added after the
> release of the qemu tree you are trying to build. Building with
> an older kernel header is equally pointless because all it would
> do is to require #ifdef magic in qemu that ends up preventing you
> from using all features of new kernels.
> 
You forgot about developers. Developer may want to use latest kvm kernel
headers to compile code that he added to qemu to use new kernel feature.

--
			Gleb.

  reply	other threads:[~2010-08-26 15:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25  0:55 [Qemu-devel] vhost_net.c broken by --kerneldir Hollis Blanchard
2010-08-25 13:37 ` Arnd Bergmann
2010-08-25 17:22   ` Hollis Blanchard
2010-08-26 15:15     ` Arnd Bergmann
2010-08-26 15:21       ` Gleb Natapov [this message]
2010-08-26 15:48         ` Anthony Liguori
2010-08-26 16:41           ` Hollis Blanchard
2010-08-26 19:01             ` Anthony Liguori
2010-08-26 15:50         ` Arnd Bergmann
2010-09-03 10:57       ` Michael S. Tsirkin
2010-08-25 17:21 ` [Qemu-devel] " Hollis Blanchard
2010-08-26  6:29   ` Gleb Natapov

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=20100826152142.GV10499@redhat.com \
    --to=gleb@redhat.com \
    --cc=arnd@arndb.de \
    --cc=hollis_blanchard@mentor.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.