From: Kashyap Chamarthy <kchamart@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] docs: add guidance on configuring CPU models for x86
Date: Mon, 25 Jun 2018 10:18:59 +0200 [thread overview]
Message-ID: <20180625081859.GC18277@paraplu> (raw)
In-Reply-To: <878t7cskaz.fsf@dusky.pond.sub.org>
On Mon, Jun 18, 2018 at 08:03:32AM +0200, Markus Armbruster wrote:
> Eduardo Habkost <ehabkost@redhat.com> writes:
>
> > On Fri, Jun 15, 2018 at 03:16:09PM +0100, Daniel P. Berrangé wrote:
> >> With the recent set of CPU hardware vulnerabilities on x86, it is
> >> increasingly difficult to understand which CPU configurations are
> >> good to use and what flaws they might be vulnerable to.
> >>
> >> This doc attempts to help management applications and administrators in
> >> picking sensible CPU configuration on x86 hosts. It outlines which of
> >> the named CPU models are good choices, and describes which extra CPU
> >> flags should be enabled to allow the guest to mitigate hardware flaws.
> >>
> >> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> >
> > Thank you very much.
> >
> > I wonder how we could reference this from the man page and
> > qemu-doc.html without saying "look at the QEMU source tree".
>
> Same way as the other contents there.
>
> > (I'm not willing to rewrite this using texinfo to make that
> > happen.)
>
> Texinfo is simple.
>
> If all else fails, ask for my help after soft freeze.
If someone already hasn't done it, I can help rewrite it. (It'll let me
try out 'Texinfo' in real and I have to deal with CPU modelling aspects
elsewhere in the higher-level tools. :-))
--
/kashyap
next prev parent reply other threads:[~2018-06-25 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 14:16 [Qemu-devel] [PATCH] docs: add guidance on configuring CPU models for x86 Daniel P. Berrangé
2018-06-15 18:58 ` Eduardo Habkost
2018-06-18 6:03 ` Markus Armbruster
2018-06-25 8:18 ` Kashyap Chamarthy [this message]
2018-06-25 8:24 ` Kashyap Chamarthy
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=20180625081859.GC18277@paraplu \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).