All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: "Wei, Gang" <gang.wei@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>
Subject: Re: [PATCH 3/5] vtdt: Modify vlapic code to add vtdt support
Date: Tue, 14 Dec 2010 08:48:51 +0000	[thread overview]
Message-ID: <C92CDFF3.CCB9%keir@xen.org> (raw)
In-Reply-To: <F26D193E20BBDC42A43B611D1BDEDE7124EADAFCDE@shsmsx502.ccr.corp.intel.com>

On 14/12/2010 08:22, "Wei, Gang" <gang.wei@intel.com> wrote:

>>> @@ -265,6 +265,7 @@ struct hvm_hw_lapic {
>>>      uint64_t             apic_base_msr;
>>>      uint32_t             disabled; /* VLAPIC_xx_DISABLED */
>>>      uint32_t             timer_divisor;
>>> +    uint64_t             tdt_msr;
>>>  };
>> 
>> Is this backward compatible with old HVM save images?
> 
> I am not sure about this. If it isn't, would you accept to simply add another
> data trunk for TDT msr?

That's Tim's call. I would personally prefer for Xen to accept truncated
chunks, and extend them with sensible 'old save image' defaults, such as
all-zeroes. That would be a generic solution to this case which will be
reusable in future, and avoid needlessly creating extra chunk types just for
backward compatibility reasons.

 -- Keir

  reply	other threads:[~2010-12-14  8:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14  3:27 [PATCH 3/5] vtdt: Modify vlapic code to add vtdt support Wei, Gang
2010-12-14  7:35 ` Keir Fraser
2010-12-14  8:22   ` Wei, Gang
2010-12-14  8:48     ` Keir Fraser [this message]
2010-12-14  9:13       ` Wei, Gang
2010-12-14  9:59         ` Keir Fraser
2010-12-14 10:01           ` Keir Fraser
2010-12-14 10:18             ` Tim Deegan
2010-12-14  9:21 ` Keir Fraser
2010-12-14  9:30   ` Wei, Gang
2010-12-14  9:56     ` Keir Fraser
2010-12-14 10:13       ` Wei, Gang
2010-12-14 10:29 ` Wei, Gang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C92CDFF3.CCB9%keir@xen.org \
    --to=keir@xen.org \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=gang.wei@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.