Re: [Xen-devel] [PATCH] x86/emulator: workaround for AMD erratum 573

[Boris Ostrovsky <boris.ostrovsky@xxxxxxx>]

On 12/16/11 03:26, Jan Beulich wrote:
> > > > On 15.12.11 at 18:52, Boris Ostrovsky<boris.ostrovsky@xxxxxxx>  wrote:
> > > --- a/xen/include/asm-x86/amd.h
> > > +++ b/xen/include/asm-x86/amd.h
> > > @@ -134,6 +134,12 @@
> > >        AMD_OSVW_ERRATUM(3, AMD_MODEL_RANGE(0x10, 0x2, 0x1, 0xff, 0xf),  \
> > >                         AMD_MODEL_RANGE(0x12, 0x0, 0x0, 0x1, 0x0))
> > >
> > > +#define AMD_ERRATUM_573                                                        
> > > \
> > > +    AMD_LEGACY_ERRATUM(AMD_MODEL_RANGE(0x0f, 0x0, 0x0, 0xff, 0xf),     \
> > > +                       AMD_MODEL_RANGE(0x10, 0x0, 0x0, 0xff, 0xf),     \
> > > +                       AMD_MODEL_RANGE(0x11, 0x0, 0x0, 0xff, 0xf),     \
> > > +                       AMD_MODEL_RANGE(0x12, 0x0, 0x0, 0xff, 0xf))
> > Families 0xf and 0x11 are not affected by erratum 573.
> Are you saying that these two documents
>
> 33610 Rev. 3.48 December 2011
> 41788 Rev. 3.10 December 2011
>
> both wrong? For fam 0xf it may be that we can set a lower bound for
> pre-NPT ones if those indeed are unaffected (but we'd like to be sure
> this is the case) - that would appear to be all with a model below 0x40.
>
> Please clarify.

Sorry, my bad. You are right --- somehow I thought it was only 10h and 12h.

-boris


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel