From: Ingo Molnar <mingo@elte.hu>
To: Avi Kivity <avi@qumranet.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] x86 updates
Date: Fri, 15 Feb 2008 09:04:33 +0100 [thread overview]
Message-ID: <20080215080433.GA12341@elte.hu> (raw)
In-Reply-To: <47B47D85.9070504@qumranet.com>
* Avi Kivity <avi@qumranet.com> wrote:
>> thanks, applied - this first looked like a KVM item, that's why i
>> havent added it. [Btw., feel free to push it via kvm.git as well - as
>> long as you are sure it does not break the build ;-) ]
>
> Yeah, I'm queuing it as well, it will get there one way or the other.
x86.git won that race ;-)
i've had a good deal of build testing done with that patch and there's
no [bzImage-level] build breakage that i can report. Which is not a
surprise, the quality of arch/x86/kvm/ is outstandingly high:
$ code-quality arch/x86/kvm/
errors lines of code errors/KLOC
arch/x86/kvm/ 29 14566 1.9
as a comparison:
errors lines of code errors/KLOC
kernel/ 729 92796 7.8
see: http://redhat.com/~mingo/x86.git/code-quality . It's as arbitrary
of a metric as all static code metrics, but the numbers it emits are
surprisingly close to my personal estimation of the cleanliness of some
in-kernel codebases i ran it again.
[ hint, try "code-quality kernel/sched.c" too ;-) ]
Ingo
next prev parent reply other threads:[~2008-02-15 8:05 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 15:57 [git pull] x86 updates Ingo Molnar
2008-02-13 16:19 ` Balbir Singh
2008-02-14 16:25 ` Ingo Molnar
2008-02-14 17:42 ` Avi Kivity
2008-02-15 3:30 ` Balbir Singh
2008-02-15 8:04 ` Ingo Molnar [this message]
2008-02-14 10:25 ` Andi Kleen
2008-02-14 15:19 ` Ingo Molnar
2008-02-14 17:10 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2009-06-20 16:49 [GIT PULL] " Ingo Molnar
2009-01-07 18:15 [git pull] " Ingo Molnar
2008-07-15 21:01 [GIT " Thomas Gleixner
2008-07-15 21:20 ` Linus Torvalds
2008-07-15 21:25 ` Ingo Molnar
2008-07-15 21:43 ` Thomas Gleixner
2008-07-15 22:00 ` Linus Torvalds
2008-07-15 22:05 ` Ingo Molnar
2008-07-15 22:14 ` Thomas Gleixner
2008-07-15 23:29 ` Linus Torvalds
2008-04-29 16:00 [git " Ingo Molnar
2008-04-26 14:21 Ingo Molnar
2008-02-29 18:08 Ingo Molnar
2008-02-25 16:27 Ingo Molnar
2008-02-19 23:13 [GIT " Thomas Gleixner
2008-02-19 23:56 ` Randy Dunlap
2008-02-20 0:06 ` Thomas Gleixner
2008-02-20 8:32 ` Ingo Molnar
2008-02-18 20:21 [GIT Pull] " Thomas Gleixner
2008-02-09 23:24 [git pull] " Thomas Gleixner
2008-02-10 1:25 ` Randy Dunlap
2008-02-10 8:03 ` Linus Torvalds
2008-02-10 9:14 ` Thomas Gleixner
2008-02-10 23:09 ` Ingo Molnar
2008-02-06 14:47 Ingo Molnar
2008-02-04 16:12 Ingo Molnar
2008-02-05 18:47 ` Linus Torvalds
2008-02-05 19:22 ` Sam Ravnborg
2008-02-05 21:05 ` Ingo Molnar
2008-02-05 21:09 ` H. Peter Anvin
2008-02-05 21:18 ` Sam Ravnborg
2008-02-05 21:23 ` H. Peter Anvin
2008-02-05 21:32 ` Linus Torvalds
2008-02-05 21:42 ` H. Peter Anvin
2008-02-05 21:17 ` Sam Ravnborg
2008-02-05 21:54 ` Ingo Molnar
2008-02-05 22:03 ` H. Peter Anvin
2008-02-05 20:12 ` H. Peter Anvin
2008-02-05 21:36 ` Ingo Molnar
2008-02-01 17:00 Ingo Molnar
2008-01-14 19:02 Ingo Molnar
2008-01-15 16:05 ` Ingo Molnar
2007-11-10 3:52 [GIT " Thomas Gleixner
2007-10-23 21:02 [Git " Thomas Gleixner
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=20080215080433.GA12341@elte.hu \
--to=mingo@elte.hu \
--cc=avi@qumranet.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.