From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>,
QEMU-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] kvm: ppc: detect old headers
Date: Tue, 03 May 2011 14:31:17 +0200 [thread overview]
Message-ID: <4DBFF595.8060607@siemens.com> (raw)
In-Reply-To: <78134E6D-50FE-483B-8B9A-6A577AC4E47B@suse.de>
On 2011-05-03 14:28, Alexander Graf wrote:
>
> On 03.05.2011, at 14:14, Jan Kiszka wrote:
>
>> On 2011-05-03 13:54, Alexander Graf wrote:
>>> When compiling Qemu with older kernel headers, the PVR setting
>>> mechanism isn't available yet. Unfortunately, back then I didn't add
>>> a capability we could check against, so all we can do is add a configure
>>> test to see if we support PVR setting. For BookE, we don't care yet.
>>>
>>> This fixes compilation errors with KVM enabled on older kernel headers
>>> (like 2.6.32).
>>
>> Why not finally import the latest kvm kernel headers into qemu? Would
>> save us a lot of current and future configure and #ifdef dances.
>
> Sure, sounds like a good topic for today's call?
Fine with me. Patch should be done by then as well.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-03 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 11:54 [Qemu-devel] [PATCH] kvm: ppc: detect old headers Alexander Graf
2011-05-03 11:54 ` [Qemu-devel] [PATCH] kvm: ppc: warn user on PAGE_SIZE mismatch Alexander Graf
2011-05-03 12:14 ` [Qemu-devel] [PATCH] kvm: ppc: detect old headers Jan Kiszka
2011-05-03 12:28 ` Alexander Graf
2011-05-03 12:31 ` Jan Kiszka [this message]
2011-05-03 12:33 ` Alexander Graf
2011-05-03 13:02 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2011-04-17 8:49 Alexander Graf
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=4DBFF595.8060607@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=scottwood@freescale.com \
/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).