From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: How to get a few MSR values from userspace? Date: Fri, 21 Dec 2012 16:08:53 +0200 Message-ID: <50D46D75.1010800@gmail.com> References: <50D459D3.4040101@gmail.com> <50D4780602000078000B204E@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50D4780602000078000B204E@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >> I need access to some MSR values that are not currently being saved in >> struct hvm_hw_cpu. Among them are MSR_IA32_MC0_CTL, MSR_IA32_MISC_ENABLE >> and MSR_IA32_ENERGY_PERF_BIAS. > > I can't see why, and this is quite likely related to the reason for > them not being accessible in the first place. Because they offer heuristic information about the type of OS running in the domU domain, and there are classes of applications interested in that. > Not to me, no. These records are use for save/restore/migrate, > and so far there hasn't been a need to include here the MSRs you > mention. Interesting. I've assumed that those would be saved (and perhaps ignored on restore if they became irrelevant) in a migration scenario. > For MSR_IA32_MC0_CTL, why not? These should be fine for > anything that is architectural to x86. > > The other two MSRs are Intel specific iirc, and hence wouldn't > be validly dealt with in vendor independent code. I agree, however, as I've said before, _some_ applications _are_ interested in vendor-specific information for heuristic purposes. Whether this would make a interesting patch for Xen or not, I would appreciate any advice on how best to implement said functionality (if only for MSR_IA32_MC0_CTL). Thanks, Razvan Cojocaru