qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/10] virtio: import headers from linux
Date: Thu, 23 May 2013 18:32:21 +0300	[thread overview]
Message-ID: <20130523153221.GA30191@redhat.com> (raw)
In-Reply-To: <20130523145643.GA24256@redhat.com>

On Thu, May 23, 2013 at 05:56:43PM +0300, Michael S. Tsirkin wrote:
> On Thu, May 23, 2013 at 03:41:07PM +0100, Peter Maydell wrote:
> > On 23 May 2013 15:34, Michael S. Tsirkin <mst@redhat.com> wrote:
> > > I'm working on adding new virtio layout to qemu.
> > > The job is complicated by the fact that
> > > qemu has its own copy of the virtio headers,
> > > sometimes with slightly different names
> > > and structure.
> > > Import headers from linux instead.
> > 
> > Do the kernel guys guarantee that their headers will
> > compile on all the platforms QEMU supports? [eg windows]
> > (this isn't an issue for the current uses of linux-headers
> > because we only use it for KVM support, and if KVM is
> > enabled you're definitely on a Linux host.)
> > 
> > thanks
> > -- PMM
> 
> No but at the moment there's nothing there besides harmless
> defines.
> 
> But it's not like we update these things automatically.
> 
> If/when things break, we can change update-headers to strip
> problematic stuff out of there.

Or so I thought but in practice there's a dependency
on linux/types.h
However, that's pretty easy to address.
I can think of two ways:
    - strip linux/types.h in update_headers
    - add a stub linux/types.h for non linux platforms

Preferences?

> -- 
> MST

  reply	other threads:[~2013-05-23 15:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 14:34 [Qemu-devel] [PATCH 00/10] virtio: import headers from linux Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 01/10] scripts/update-linux-headers.sh: add virtio Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 02/10] virtio-9p: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 03/10] virtio-net, eth: use linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 04/10] virtio-blk: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:34 ` [Qemu-devel] [PATCH 05/10] virtio-balloon: " Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 06/10] virtio-rng: " Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 07/10] virtio-console: " Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 08/10] virtio: add virtio_ids from linux-headers Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 09/10] virtio-pci: switch to linux-headers Michael S. Tsirkin
2013-05-23 14:35 ` [Qemu-devel] [PATCH 10/10] virtio: use ring structure from linux-headers Michael S. Tsirkin
2013-05-23 14:41 ` [Qemu-devel] [PATCH 00/10] virtio: import headers from linux Peter Maydell
2013-05-23 14:56   ` Michael S. Tsirkin
2013-05-23 15:32     ` Michael S. Tsirkin [this message]
2013-05-23 15:58       ` Paolo Bonzini

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=20130523153221.GA30191@redhat.com \
    --to=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).