All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Request to enable SMP and virtio for qemux86/x86-64
Date: Tue, 17 Jan 2012 09:06:06 -0500	[thread overview]
Message-ID: <4F15804E.4020009@windriver.com> (raw)
In-Reply-To: <4F0EDC9F.4050502@intel.com>

On 12-01-12 08:14 AM, Zhai, Edwin wrote:
> Bruce,
> Thanks for your efforts!

FYI: I haven't forgotten about this, I'm just reworking a few
things with the 3.2 kernel tree, and will include this as part
of that effort. It will all be available soon.

Bruce

>
> Edwin
>
> On 2012/1/11 20:43, Bruce Ashfield wrote:
>> On 12-01-11 02:01 AM, Zhai, Edwin wrote:
>>> Bruce,
>>> Can we enable SMP and virtio by default for qemux86/x86-64? This can
>>> achieve
>>> huge perf boost for workload inside qemu. E.g. we enabled self-hosted
>>> image,
>>> where we build yocto inside qemu.
>>>
>>> Attached patch showes the kernel config option.
>>>
>>> Is it reasonable?
>>
>> It should be. I just need to look at the fallback modes, and how this
>> impacts different host systems. That being said, I've run with similar
>> configs in the past (depending on the workload) with no issues.
>>
>> qemux8-64 is already SMP, so it would just need the addition of virtio
>> devices, which just means we'd look at this as any BSP/target config
>> update.
>>
>> But with graceful degradation (i.e maxcpus with SMP set) and agreement
>> that we'd like to simulate SMP by default, then we can make the change
>> and I'll merge it into the base config for the target and pull it into
>> the kernel tree.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>>
>>
>>>
>>> Thanks,
>>> Edwin
>>>
>>
>



  reply	other threads:[~2012-01-17 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  7:01 Request to enable SMP and virtio for qemux86/x86-64 Zhai, Edwin
2012-01-11 12:43 ` Bruce Ashfield
2012-01-12 13:14   ` Zhai, Edwin
2012-01-17 14:06     ` Bruce Ashfield [this message]
2012-01-26  4:49       ` 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=4F15804E.4020009@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=edwin.zhai@intel.com \
    --cc=yocto@yoctoproject.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.