From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <darren.hart@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] runqemu: Use correct kvm CPU options for qemux86* with kvm
Date: Wed, 25 Sep 2013 22:09:47 +0100 [thread overview]
Message-ID: <1380143387.18603.347.camel@ted> (raw)
In-Reply-To: <1380143117.4035.144.camel@dvhart-mobl4.amr.corp.intel.com>
On Wed, 2013-09-25 at 14:05 -0700, Darren Hart wrote:
> On Wed, 2013-09-25 at 21:59 +0100, Richard Purdie wrote:
> > The existing -cpu host option caused kernel panics when people attempted to use
> > the kvm option. After research and discussion, the best options appear to
> > be the kvm32/kvm64 cpu types so lets use these instead. These resolve
> > the kernel issues for me.
> >
> > [YOCTO #3908]
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Makes a lot of sense to me:
>
> Acked-by: Darren Hart <dvhart@linux.intel.com>
>
> > ---
> > diff --git a/scripts/runqemu b/scripts/runqemu
> > index efab1a2..12c58d9 100755
> > --- a/scripts/runqemu
> > +++ b/scripts/runqemu
> > @@ -265,7 +265,11 @@ if [ "x$KVM_ENABLED" = "xyes" ]; then
> > exit 1;
> > fi
> > if [ -w /dev/kvm -a -r /dev/kvm ]; then
> > - SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu host"
> > + if [ "x$MACHINE" = "xqemux86" ]; then
> > + SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu kvm32"
> > + elif [ "x$MACHINE" = "xqemux86-64" ]; then
> > + SCRIPT_QEMU_OPT="$SCRIPT_QEMU_OPT -enable-kvm -cpu kvm64"
> > + fi
>
> The above is fine, but it does raise the question of dealing with non
> oe-core BSPs with runqemu. For instance, there would be value in testing
> genericx86 and genericx86_64 in the same way. We can deal with that
> separately though I think as this solves an immediate problem and
> doesn't make it any worse for the case I mention.
There is an explicit check for qemux86* just above this block so whilst
I like the idea, its something for another patch and likely 1.6
material. Could be worth an enhancement bug though.
Cheers,
Richard
next prev parent reply other threads:[~2013-09-25 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 20:59 [PATCH] runqemu: Use correct kvm CPU options for qemux86* with kvm Richard Purdie
2013-09-25 21:05 ` Darren Hart
2013-09-25 21:09 ` Richard Purdie [this message]
2013-09-25 21:32 ` Darren Hart
2013-09-25 21:34 ` Khem Raj
2013-09-25 22:00 ` Richard Purdie
2013-09-25 22:05 ` Khem Raj
2013-09-26 4:26 ` Bruce Ashfield
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=1380143387.18603.347.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=darren.hart@intel.com \
--cc=openembedded-core@lists.openembedded.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.