From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Maxim Levitsky <mlevitsk@redhat.com>,
Yang Zhong <yang.zhong@linux.intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Jing Liu <jing2.liu@intel.com>
Subject: Re: [PATCH 0/2] target/i386: add support for cpu FLUSH_L1D feature and FB_CLEAR capability
Date: Mon, 8 May 2023 17:04:13 +0200 [thread overview]
Message-ID: <54d6c865-d518-e68c-63d6-0175c715556f@redhat.com> (raw)
In-Reply-To: <20230201135759.555607-1-eesposit@redhat.com>
Ping?
Am 01/02/2023 um 14:57 schrieb Emanuele Giuseppe Esposito:
> QEMU should be able to show the guest the above feature/capability,
> otherwise we risk to have false vulnerability reports in the guest like in
> /sys/devices/system/cpu/vulnerabilities/mmio_stale_data
> because the mitigation is present only if the guest supports
> (FLUSH_L1D and MD_CLEAR) or FB_CLEAR.
>
> Emanuele
>
> Emanuele Giuseppe Esposito (2):
> target/i386: add support for FLUSH_L1D feature
> target/i386: add support for FB_CLEAR feature
>
> target/i386/cpu.h | 3 +++
> target/i386/cpu.c | 4 ++--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2023-05-08 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:57 [PATCH 0/2] target/i386: add support for cpu FLUSH_L1D feature and FB_CLEAR capability Emanuele Giuseppe Esposito
2023-02-01 13:57 ` [PATCH 1/2] target/i386: add support for FLUSH_L1D feature Emanuele Giuseppe Esposito
2023-02-01 13:57 ` [PATCH 2/2] target/i386: add support for FB_CLEAR feature Emanuele Giuseppe Esposito
2023-05-08 15:04 ` Emanuele Giuseppe Esposito [this message]
2023-05-09 9:05 ` [PATCH 0/2] target/i386: add support for cpu FLUSH_L1D feature and FB_CLEAR capability Paolo Bonzini
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=54d6c865-d518-e68c-63d6-0175c715556f@redhat.com \
--to=eesposit@redhat.com \
--cc=jing2.liu@intel.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vkuznets@redhat.com \
--cc=yang.zhong@linux.intel.com \
/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).