On Thu, Nov 14, 2013 at 01:39:30PM +0200, Michael S. Tsirkin wrote:
On Wed, Oct 09, 2013 at 08:33:40PM -0400, Kevin O'Connor wrote:
On Thu, Oct 03, 2013 at 04:06:24PM +0300, Michael S. Tsirkin wrote:
IASL stores it's revision in each table header it generates.
That's a problem since
On Thu, Oct 03, 2013 at 04:06:24PM +0300, Michael S. Tsirkin wrote:
IASL stores it's revision in each table header it generates.
That's a problem since guests see a change each time
they move between hypervisors.
We generally fill our own info for tables,
but we forgot to do this for the
On Wed, Oct 09, 2013 at 08:33:40PM -0400, Kevin O'Connor wrote:
On Thu, Oct 03, 2013 at 04:06:24PM +0300, Michael S. Tsirkin wrote:
IASL stores it's revision in each table header it generates.
That's a problem since guests see a change each time
they move between hypervisors.
We generally
IASL stores it's revision in each table header it generates.
That's a problem since guests see a change each time
they move between hypervisors.
We generally fill our own info for tables,
but we forgot to do this for the built-in DSDT.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
