From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: ***UNCHECKED*** [patch 0/8] MDD v1.3.1
Date: Wed, 18 Apr 2018 18:39:20 +0200 [thread overview]
Message-ID: <20180418163920.GJ4290@pd.tnic> (raw)
In-Reply-To: <20180418141553.E0B2F61133@crypto-ml.lab.linutronix.de>
On Thu, Apr 12, 2018 at 10:26:49PM -0400, speck for konrad.wilk_at_oracle.com wrote:
> - No AMD SVM support as I don't know the bits.
Now you do and I'm guessing we should do it per-guest, if the guest
kernel boots with mdd=on, we should handle the WRMSR properly and do the
write on the host CPU.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2018-04-18 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180418141553.E0B2F61133@crypto-ml.lab.linutronix.de>
2018-04-18 16:20 ` [MODERATED] Re: [patch 0/8] MDD v1.3.1 Borislav Petkov
2018-04-18 16:39 ` Borislav Petkov [this message]
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=20180418163920.GJ4290@pd.tnic \
--to=bp@suse.de \
--cc=speck@linutronix.de \
/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.