On 16/10/2018 19:54, Andrew Cooper wrote:
> Hello,
>
> I realise this is an old CPU, but I've I've encountered a weird failure
> on it.
>
> Specifically:
>
> (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 23 (0x17), Stepping 6
> (raw 00010676)
> [root@harpertown ~]# head /proc/cpuinfo
Just to foll
On 18/12/2018 11:37, Jan Beulich wrote:
On 18.12.18 at 10:56, wrote:
>> On 18/12/2018 02:17, Tian, Kevin wrote:
From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
Sent: Monday, December 17, 2018 10:21 PM
On 17/12/2018 13:09, Andrew Cooper wrote:
> On 17/12/2018 02:
>>> On 18.12.18 at 10:56, wrote:
> On 18/12/2018 02:17, Tian, Kevin wrote:
>>> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
>>> Sent: Monday, December 17, 2018 10:21 PM
>>>
>>> On 17/12/2018 13:09, Andrew Cooper wrote:
On 17/12/2018 02:39, Tian, Kevin wrote:
After some inve
On 18/12/2018 02:17, Tian, Kevin wrote:
>> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
>> Sent: Monday, December 17, 2018 10:21 PM
>>
>> On 17/12/2018 13:09, Andrew Cooper wrote:
>>> On 17/12/2018 02:39, Tian, Kevin wrote:
>>> After some investigation, it turns out that after vmentry
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, December 17, 2018 10:21 PM
>
> On 17/12/2018 13:09, Andrew Cooper wrote:
> > On 17/12/2018 02:39, Tian, Kevin wrote:
> > After some investigation, it turns out that after vmentry, while the
> > load list has the value
On 17/12/2018 13:09, Andrew Cooper wrote:
> On 17/12/2018 02:39, Tian, Kevin wrote:
> After some investigation, it turns out that after vmentry, while the
> load list has the value 0xd01 (NXE, LMA, LME, SCE), the value loaded
> into hardware is 0xd00 (NXE, LMA, LME).
>
> I.e. wh
On 17/12/2018 02:39, Tian, Kevin wrote:
After some investigation, it turns out that after vmentry, while the
load list has the value 0xd01 (NXE, LMA, LME, SCE), the value loaded
into hardware is 0xd00 (NXE, LMA, LME).
I.e. when an MSR load list is used for EFER, we resume t
> From: Tian, Kevin
> Sent: Tuesday, December 11, 2018 3:10 PM
>
> > From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> > Sent: Tuesday, December 11, 2018 1:13 AM
> >
> > Ping Kevin / Jun.
> >
> > On 16/10/2018 19:54, Andrew Cooper wrote:
> > > Hello,
> > >
> > > I realise this is an old CPU
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Tuesday, December 11, 2018 1:13 AM
>
> Ping Kevin / Jun.
>
> On 16/10/2018 19:54, Andrew Cooper wrote:
> > Hello,
> >
> > I realise this is an old CPU, but I've I've encountered a weird failure
> > on it.
> >
> > Specifically:
> >
>
Ping Kevin / Jun.
On 16/10/2018 19:54, Andrew Cooper wrote:
> Hello,
>
> I realise this is an old CPU, but I've I've encountered a weird failure
> on it.
>
> Specifically:
>
> (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 23 (0x17), Stepping 6
> (raw 00010676)
> [root@harpertown ~]# head /proc/cp
On 05/11/18 16:25, Ian Jackson wrote:
> Andrew Cooper writes ("[Xen-devel] MSR load lists on Harpertown"):
>> I realise this is an old CPU, but I've I've encountered a weird failure
>> on it.
> ...
>> However, given this behaviour, I can't think
Andrew Cooper writes ("[Xen-devel] MSR load lists on Harpertown"):
> I realise this is an old CPU, but I've I've encountered a weird failure
> on it.
...
> However, given this behaviour, I can't think of any way to context
> switch NX properly, and leave 64b
Hello,
I realise this is an old CPU, but I've I've encountered a weird failure
on it.
Specifically:
(XEN) CPU Vendor: Intel, Family 6 (0x6), Model 23 (0x17), Stepping 6
(raw 00010676)
[root@harpertown ~]# head /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model
13 matches
Mail list logo
