On Fri, Dec 18, 2015 at 12:25 PM, Andy Lutomirski wrote:
> [cc: John Stultz -- maybe you have ideas on how this should best
> integrate with the core code]
>
> On Fri, Dec 18, 2015 at 11:45 AM, Marcelo Tosatti wrote:
>> On Fri, Dec 18, 2015 at 11:27:13AM -0800, Andy Lutomirski
hosts that have a reliable TSC. Add it back; and since the field boot_ns
>> is not anymore related to the host boot-based clock, rename
>> boot_ns->nsec_base
>> and the existing nsec_base->snsec_base.
>>
>> Cc: Thomas Gleixner
>> Cc: John Stultz
>> Re
keeping code, especially after resume.
>
> Remove this code from random.c and add the appropriate
> add_device_randomness calls to timekeeping.c instead.
>
> Cc: John Stultz
> Signed-off-by: Andy Lutomirski
> ---
> drivers/char/random.c | 2 --
> kernel/time/timekeeping.c
notifier method is interesting, and if
it works well, we may want to extend it later to cover the vsyscall code
too, but that can be done in a later iteration.
Acked-by: John Stultz
thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a
On 10/24/2012 06:13 AM, Marcelo Tosatti wrote:
As suggested by John, export time data similarly to how its
done by vsyscall support. This allows KVM to retrieve necessary
information to implement vsyscall support in KVM guests.
Signed-off-by: Marcelo Tosatti
Thanks Marcelo, I like this much bet
On 09/30/2012 04:59 AM, Fengguang Wu wrote:
On Sun, Sep 30, 2012 at 01:32:46PM +0200, Avi Kivity wrote:
On 09/30/2012 01:23 PM, Fengguang Wu wrote:
On Sun, Sep 30, 2012 at 01:10:55PM +0200, Avi Kivity wrote:
On 09/28/2012 05:35 AM, Paul E. McKenney wrote:
On Thu, Sep 27, 2012 at 12:40:44PM +0
On Fri, 2010-08-20 at 14:52 -1000, Zachary Amsden wrote:
> I think gettimefromboot_ns() is a good descriptive name, but slightly
> too long - it would ruin my indentation. Perhaps getrealtime_ns()?
Sigh... So getrealtime_ns would probably be confused with
CLOCK_REALTIME, which is wall time. :P
On Fri, 2010-08-20 at 13:37 -1000, Zachary Amsden wrote:
> On 08/20/2010 08:39 AM, john stultz wrote:
> > On Thu, 2010-08-19 at 22:07 -1000, Zachary Amsden wrote:
> >
> >> Add a kernel call to get the number of nanoseconds since boot. This
> >> is generally u
On Thu, 2010-08-19 at 22:07 -1000, Zachary Amsden wrote:
> Add a kernel call to get the number of nanoseconds since boot. This
> is generally useful enough to make it a generic call.
Few comments here.
> Signed-off-by: Zachary Amsden
> ---
> include/linux/time.h |1 +
> kernel/time/ti
On Tue, 2010-06-15 at 11:03 -1000, Zachary Amsden wrote:
> On 06/14/2010 10:41 PM, Avi Kivity wrote:
> > On 06/15/2010 10:34 AM, Zachary Amsden wrote:
> >> Add a helper function for the multiple places this is used. Note
> >> that it
> >> must not be called in preemptible context, as that would m
On Fri, 2010-05-28 at 02:33 +0200, Bernhard Schmidt wrote:
> On 28.05.2010 02:00, john stultz wrote:
> > Looking at the diff:
> > --- dmesg-lenny 2010-05-27 16:45:33.0 -0700
> > +++ dmesg-squeeze 2010-05-27 16:46:14.0 -0700
> > @@ -132,8 +13
On Thu, 2010-05-27 at 23:48 +0200, Bernhard Schmidt wrote:
> On 27.05.2010 21:08, john stultz wrote:
> > I'd be very interested in hearing more about the host side issue. So
> > this happened with the same kernel that you were using before, with no
> > trouble?
>
>
On Thu, May 27, 2010 at 11:32 AM, Bernhard Schmidt wrote:
> Alexander Graf wrote:
>> Do you have ntpd running inside the guest? I have a bug report lying
>> around about 2.6.33 with kvm-clock jumping in time when ntpd is used:
>> https://bugzilla.novell.com/show_bug.cgi?id=582260
>
> I want to ch
On Wed, 2008-06-18 at 19:41 -0300, Marcelo Tosatti wrote:
> On Wed, Jun 18, 2008 at 04:42:40PM -0500, Anthony Liguori wrote:
> > Marcelo Tosatti wrote:
> >> On Wed, Jun 18, 2008 at 04:02:39PM -0500, Anthony Liguori wrote:
> >>
> > Have we yet determined why the TSC is so unstable in the fir
On Sun, 2008-06-01 at 14:56 -0300, Marcelo Tosatti wrote:
> On Sun, Jun 01, 2008 at 06:34:27PM +0200, Thomas Gleixner wrote:
> > On Thu, 29 May 2008, Marcelo Tosatti wrote:
> > > KVM wishes to allow direct guest access to the ACPI pmtimer. In that
> > > case QEMU/KVM has to read the current value f
15 matches
Mail list logo
