[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 3/5] vtdt: Modify vlapic code to add vtdt support
- To: "Wei, Gang" <gang.wei@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <keir@xxxxxxx>
- Date: Tue, 14 Dec 2010 09:56:49 +0000
- Cc:
- Delivery-date: Tue, 14 Dec 2010 01:59:37 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=nq89pPKbShNnEsStoEKN0oW/taU+uQ2qJx5asWkY/ka244161WTZrlpzGKYkHqtyfE aJfriMaaGR4IqETuNcDVN0zSjDcj1Jf7I7txlBhAFR4phljJsZ5AzOvd/sSZquddj8MT RMpYUiGT6veFrtn+e2ulpR2Gwo2JMzc42T2WU=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcubPslPXD79XKNoRpanX8il5iAsXgAMXEvzAAAbfHAAASRLwA==
- Thread-topic: [Xen-devel] [PATCH 3/5] vtdt: Modify vlapic code to add vtdt support
On 14/12/2010 09:30, "Wei, Gang" <gang.wei@xxxxxxxxx> wrote:
>> Writing any value to LVTT zaps TMICT,TMCCT,MSR_TDT? That seems pretty
>> unlikely to me! This obviously has effects on behaviour outside TDT
>> emulation as it affects TMICT/TMCCT emulation. Looks dangerous, as well as
>> wrong.
>
> It should be better to do the zaps only while the mode bits of LVTT changes.
What is real hardware behaviour here? I don't see any zappings documented.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
