[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+8MBbLh2JyWg=AF-cftrCfDB8QgRwJ2sKV-S24Jqtu_y1qZrg@mail.gmail.com>
Date: Wed, 9 Jan 2019 10:41:47 -0800
From: Tony Luck <tony.luck@...il.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Reinette Chatre <reinette.chatre@...el.com>,
Babu Moger <Babu.Moger@....com>, X86-ML <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Fenghua Yu <fenghua.yu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jan H. Schönherr <jschoenh@...zon.de>,
David Duncan <davdunc@...zon.com>
Subject: Re: [PATCH] x86/intel_rdt: use rdmsr_safe() to workaround AWS host issue
On Wed, Jan 9, 2019 at 5:00 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Wed, Jan 09, 2019 at 01:09:31PM +0100, Vitaly Kuznetsov wrote:
> > Hm, why is that? In theory, hypervisors can pass through or emulate the
> > required MSRs...
>
> ...and when the theory becomes reality we'll remove the check.
In practice that may be a long time coming. We don't have many CLOSIDs, or
bits in a cache mask, at the h/w level. If you start trying to
subdivide those resources
to pass a subset to a guest, then you'll quickly find that you have no
flexibility in the
guest to do anything useful. It would only work if you limited to
two, or perhaps three
guests.
-Tony
Powered by blists - more mailing lists