qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] docs: add guidance on configuring CPU models for x86
Date: Fri, 15 Jun 2018 15:58:05 -0300	[thread overview]
Message-ID: <20180615185805.GE7451@localhost.localdomain> (raw)
In-Reply-To: <20180615141609.20749-1-berrange@redhat.com>

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".

(I'm not willing to rewrite this using texinfo to make that
happen.)


-- 
Eduardo

  reply	other threads:[~2018-06-15 18:58 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 [this message]
2018-06-18  6:03   ` Markus Armbruster
2018-06-25  8:18     ` Kashyap Chamarthy
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=20180615185805.GE7451@localhost.localdomain \
    --to=ehabkost@redhat.com \
    --cc=berrange@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).