[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <461C0F76.1070308@vmware.com>
Date: Tue, 10 Apr 2007 15:28:06 -0700
From: Zachary Amsden <zach@...are.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: Chris Wright <chrisw@...s-sol.org>, Andrew Morton <akpm@...l.org>,
Andi Kleen <ak@....de>, Rusty Russell <rusty@...tcorp.com.au>,
Virtualization Mailing List <virtualization@...ts.osdl.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dan Hecht <dhecht@...are.com>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 9/10] Vmi timer update.patch
Jeremy Fitzhardinge wrote:
> Why not submit a patch to do what you need here? (The Geode comment is
> a bit worrying though.)
>
Why should VMI add workaround into PIT code? PIT code wants to know
nothing about VMI. It understands PIT timers on hardware. VMI, on the
other hand, is special - it knows exactly what hardware platform it has
and can manipulate hardware freely. On a generic platform, surely touch
PIT I/O ports would be quite ill behavior. But side effects of that on
a vastly restricted platform are predictable based on the hardware and
kernel, and we would not add a workaround outside of VMI unless it was
really necessary or generally useful.
Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists