On Wed, 7 Sep 2016, Ian Jackson wrote: > > Technical > > ========= > > On the technical front, it would be good to understand whether > > a) This is a real threat and whether thus, we as a community need to > > take action > > It is unclear what action the Xen upstream community can usefully > take, other than providing users with information. > > But, users with deployments on actual hardware ought to try to find > out whether they are vulnerable. If they are then they could seek > replacement non-faulty hardware from their vendor, or take unpleasant > migitation measures (like switching to HVM, perhaps).
How difficult is to check for it? Is there a simple test, maybe a little executable, that users could use to find out whether their ram is vulnerable? That would be extremely valuable. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
