From: Zachary Amsden <zach@vmware.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
virtualization@lists.osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>
Subject: Re: [PATCH 1/5] Skip timer works.patch
Date: Mon, 30 Oct 2006 12:54:55 -0800 [thread overview]
Message-ID: <4546669F.8020706@vmware.com> (raw)
In-Reply-To: <200610271416.12548.ak@suse.de>
Andi Kleen wrote:
> no_timer_check. But it's only there on x86-64 in mainline - although there
> were some patches to add it to i386 too.
>
I can rename to match the x86-64 name.
>> That is what this patch is building towards, but the boot option is
>> "free", so why not? In the meantime, it helps non-paravirt kernels
>> booted in a VM.
>>
>
> Hmm, you meant they paniced before? If they just fail a few tests
> that is not particularly worrying (real hardware does that often too)
>
Yes, they sometimes fail to boot, and the failure message used to ask us
to pester mingo.
Zach
next prev parent reply other threads:[~2006-10-30 20:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 0:09 [PATCH 1/5] Skip timer works.patch Zachary Amsden
2006-10-27 14:56 ` Andi Kleen
2006-10-27 19:09 ` Zachary Amsden
2006-10-27 21:16 ` Andi Kleen
2006-10-30 20:54 ` Zachary Amsden [this message]
2006-10-30 22:50 ` Andi Kleen
2006-10-30 23:09 ` Zachary Amsden
2006-10-30 23:12 ` Andi Kleen
2006-10-30 23:24 ` Zachary Amsden
2006-10-30 23:50 ` Andi Kleen
2006-11-15 8:03 ` Chris Wright
2006-11-15 8:21 ` Zachary Amsden
2006-11-15 22:40 ` Chris Wright
2006-11-15 22:54 ` Chris Wright
2006-11-16 3:27 ` Andi Kleen
2006-11-16 3:37 ` Chris Wright
2006-11-16 3:37 ` Andi Kleen
2006-11-16 5:06 ` Andrew Morton
2006-11-16 6:13 ` Zachary Amsden
2006-11-16 7:23 ` Andi Kleen
2006-11-16 7:02 ` Andi Kleen
2006-11-16 7:16 ` Chris Wright
2006-11-16 8:26 ` Chris Wright
2006-11-16 10:28 ` Chris Wright
2006-11-16 13:16 ` Andi Kleen
2006-11-16 19:03 ` Chris Wright
2006-11-16 19:46 ` Andi Kleen
2006-11-16 20:24 ` Chris Wright
2006-11-17 4:47 ` Andi Kleen
2006-11-17 7:33 ` Chris Wright
2006-11-17 7:38 ` Andi Kleen
2006-11-16 22:53 ` Andrew Morton
2006-11-16 23:08 ` Zachary Amsden
2006-11-16 23:10 ` Chris Wright
2006-11-17 5:05 ` Andi Kleen
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=4546669F.8020706@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).