From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] build: introduce target CONFIG_ variables and use them for kvm
Date: Sun, 01 Jul 2012 15:37:18 +0200 [thread overview]
Message-ID: <4FF0528E.6000307@redhat.com> (raw)
In-Reply-To: <CAFEAcA9YvxTWCiWVAcveOsVbHoJP79kFSLZniB8Vb91fmk4FOg@mail.gmail.com>
Il 23/06/2012 12:30, Peter Maydell ha scritto:
>> > Can't it go in hw/arm/kvm (mimicking the final desired place, which
>> > will be target-arm/hw/kvm)? And hw/kvm can be moved to hw/i386/kvm, or
>> > we can leave it there for now until we're ready to move it to
>> > target-i386/hw/kvm.
> Why's the final desired place target-arm/hw/kvm ? That doesn't
> make much sense to me...
Doesn't it have some dependency on target-arm/kvm.c?
Paolo
next prev parent reply other threads:[~2012-07-01 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:31 [Qemu-devel] [PATCH] build: introduce target CONFIG_ variables and use them for kvm Paolo Bonzini
2012-06-21 13:06 ` Anthony Liguori
2012-06-23 7:53 ` Paolo Bonzini
2012-06-23 10:30 ` Peter Maydell
2012-07-01 13:37 ` Paolo Bonzini [this message]
2012-07-01 13:49 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2012-06-20 14:44 Anthony Liguori
2012-06-20 14:51 ` Andreas Färber
2012-06-20 15:01 ` Peter Maydell
2012-06-20 15:04 ` Andreas Färber
2012-06-20 15:07 ` Peter Maydell
2012-06-20 15:23 ` Andreas Färber
2012-06-20 15:20 ` Anthony Liguori
2012-06-20 15:09 ` Peter Maydell
[not found] ` <CAFEAcA-MgQuEfca7bPtUrN-wwN0KVCvXWpcs8Y4tdWL+CbcGFw@mail.gmail.com>
[not found] ` <4FEDA01B.8010502@suse.de>
2012-07-01 14:10 ` Paolo Bonzini
[not found] ` <4FEDB5F0.1070407@codemonkey.ws>
2012-07-23 14:21 ` Peter Maydell
2012-07-31 17:28 ` Peter Maydell
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=4FF0528E.6000307@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--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 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.