lkml.org 
[lkml]   [2011]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] x86, efi: Don't recursively acquire rtc_lock
On 08/08/2011 04:40 PM, Matt Fleming wrote:
> On Fri, 2011-08-05 at 18:04 +0100, Jan Beulich wrote:
> >
> > Virtual platforms will have to take care of the serialization in the
> > host anyway, so the guest side implementation of getwallclock et al
> > is entirely unaffected.
>
> Ah, OK, that's the important part. I didn't realise that rtc_lock isn't
> actually required by any other code. In which case, yes, it completely
> makes sense to push the locking of rtc_lock down into the
> implementations that actually need it.
>
> It'd be great if I could get some ACK's from the virtualization guys.

Ack (for that aspect).

--
error compiling committee.c: too many arguments to function



\
 
 \ /
  Last update: 2011-08-08 16:21    [W:0.078 / U:0.696 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site