mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Gleb Natapov <gleb@kernel.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 3.17-rc4
Date: Sat, 6 Sep 2014 00:43:17 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1409060042020.5472@nanos> (raw)
In-Reply-To: <540A2F15.5070603@redhat.com>

On Fri, 5 Sep 2014, Paolo Bonzini wrote:

> Il 05/09/2014 23:24, Thomas Gleixner ha scritto:
> > 
> >> > that besides acting as a workaround, I find the patched code easier to
> >> > understand, and I clearly stated the same in the tag message.
> > Well, we might have different opinions about easier to understand. I
> > did go a great length to distangle the monotonic boot time on which
> > you are interested from xtime, because the latter does not make any
> > sense outside of the core timekeeping code. Aside of that I optimized
> > the whole thing to avoid conversions, loops and hoops. So you just add
> > another multiply and add to make it more understandable. 
> 
> Fair enough, I've dropped the patch.

Though I agree that the struct member name choice is not the most
brilliant one, so feel free to fix that.
 
> Thanks for helping out with the core timekeeping fix.

I'm still banging my head against the wall....

      reply	other threads:[~2014-09-05 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 10:16 Paolo Bonzini
2014-09-05 20:44 ` Linus Torvalds
2014-09-05 20:58   ` Thomas Gleixner
2014-09-05 21:09     ` Paolo Bonzini
2014-09-05 21:24       ` Thomas Gleixner
2014-09-05 21:45         ` Paolo Bonzini
2014-09-05 22:43           ` Thomas Gleixner [this message]

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=alpine.DEB.2.10.1409060042020.5472@nanos \
    --to=tglx@linutronix.de \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®