From: Stefan Weil <weil@mail.berlios.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Cam Macdonell <cam@cs.ualberta.ca>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v8 5/5] RESEND: Inter-VM shared memory PCI device
Date: Wed, 11 Aug 2010 20:22:57 +0200 [thread overview]
Message-ID: <4C62EA81.5040206@mail.berlios.de> (raw)
In-Reply-To: <4C62D8C1.6000801@redhat.com>
Am 11.08.2010 19:07, schrieb Paolo Bonzini:
> On 08/11/2010 11:49 AM, Cam Macdonell wrote:
>>> The win32 problems (missing mmap, maybe more) remain.
>>> Could you please fix them?
>>
>> Could that be accomplished with excluding it on Windows on the
>> makefiles?
>
> Yes, just use obj-$(CONFIG_POSIX).
>
> Paolo
>
Or use obj-$(CONFIG_KVM) if that file is only reasonable when KVM is
supported.
Stefan
next prev parent reply other threads:[~2010-08-11 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 0:10 [Qemu-devel] [PATCH v8 0/5] Inter-VM Shared Memory Device Cam Macdonell
2010-07-27 0:10 ` [Qemu-devel] [PATCH v8 1/5] Add qemu_ram_alloc_from_ptr function Cam Macdonell
2010-07-27 0:10 ` [Qemu-devel] [PATCH v8 2/5] Device specification for shared memory PCI device Cam Macdonell
2010-07-27 0:10 ` [Qemu-devel] [PATCH v8 3/5] Add function to assign ioeventfd to MMIO Cam Macdonell
2010-07-27 0:11 ` [Qemu-devel] [PATCH v8 4/5] Support marking a device as non-migratable Cam Macdonell
2010-07-27 0:11 ` [Qemu-devel] [PATCH v8 5/5] Inter-VM shared memory PCI device Cam Macdonell
2010-07-27 16:54 ` [Qemu-devel] [PATCH v8 5/5] RESEND: " Cam Macdonell
2010-08-11 8:35 ` Stefan Weil
2010-08-11 15:49 ` Cam Macdonell
2010-08-11 17:07 ` Paolo Bonzini
2010-08-11 18:22 ` Stefan Weil [this message]
2010-08-10 21:28 ` [Qemu-devel] [PATCH v8 1/5] Add qemu_ram_alloc_from_ptr function Anthony Liguori
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=4C62EA81.5040206@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=aliguori@us.ibm.com \
--cc=cam@cs.ualberta.ca \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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).