From: Mike Day <ncmike@ncultra.org>
To: Alexander Graf <agraf@suse.de>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Paul Mackerras <paulus@samba.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH v2] PPC: smp: autodetect numbers of threads per core
Date: Fri, 10 Jan 2014 09:12:09 -0500 [thread overview]
Message-ID: <8761psexja.fsf@pixel.localdomain> (raw)
In-Reply-To: <84B5F34E-6072-4E56-8493-AAC69B9F7DAE@suse.de>
Alexander Graf <agraf@suse.de> writes:
>> The patch as it its now is very simple and well-contained. I wonder how
>> much it would expand if we added a max thread count to the cpu class. It
>> seems like the need for a max thread count is idiomatic to powerpc.
>
> It's only ever useful on IBM POWER. Any other PowerPC system can partition vcpus by host threads, it's only IBM POWER hardware that's as broken as it is.
> I do see that the user experience is slightly suboptimal, but by creating this special case there's a good chance you're doing more harm than good.
All the problems you raise about special cases are true. But, as you
point out, ibm power is uniquely broken, which would possibly justify a
special case, unless there is a better general solution. In other words,
special cases exist for unique circumstances and if I understand you
correctly this is a unique circumstance.
Alexy explained the use case in his initial posting. The user needs to
allocate all threads of a core to an instance of KVM, but has no easy
way to obtain that information (threads per core) for the Qemu threads
option. So specifying threads="max" is a more user-friendly option. In
my understanding this is strictly a usability issue.
Mike
--
Mike Day | "Endurance is a Virtue"
next prev parent reply other threads:[~2014-01-10 14:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 5:34 [Qemu-devel] [RFC PATCH v2] PPC: smp: autodetect numbers of threads per core Alexey Kardashevskiy
2014-01-09 21:00 ` Mike Day
2014-01-09 22:12 ` Alexey Kardashevskiy
2014-01-09 23:40 ` Alexander Graf
2014-01-10 1:39 ` Alexey Kardashevskiy
2014-01-10 13:03 ` Mike Day
2014-01-10 13:28 ` Alexander Graf
2014-01-10 13:42 ` Alexey Kardashevskiy
2014-01-10 14:00 ` Alexander Graf
2014-01-10 14:13 ` Alexey Kardashevskiy
2014-01-10 14:20 ` Alexander Graf
2014-01-10 14:21 ` Mike Day
2014-01-10 14:25 ` Alexander Graf
2014-01-10 14:29 ` Mike Day
2014-01-10 14:35 ` Alexey Kardashevskiy
2014-01-10 14:12 ` Mike Day [this message]
2014-01-09 22:50 ` Scott Wood
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=8761psexja.fsf@pixel.localdomain \
--to=ncmike@ncultra.org \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.