From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>, Thomas Gleixner <tglx@linutronix.de>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 9/10] Vmi timer update.patch
Date: Tue, 10 Apr 2007 15:28:06 -0700 [thread overview]
Message-ID: <461C0F76.1070308@vmware.com> (raw)
In-Reply-To: <461C0CB4.9000407@goop.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>, Rusty Russell <rusty@rustcorp.com.au>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dan Hecht <dhecht@vmware.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 9/10] Vmi timer update.patch
Date: Tue, 10 Apr 2007 15:28:06 -0700 [thread overview]
Message-ID: <461C0F76.1070308@vmware.com> (raw)
In-Reply-To: <461C0CB4.9000407@goop.org>
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
next prev parent reply other threads:[~2007-04-10 22:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 0:06 [PATCH 9/10] Vmi timer update.patch Zachary Amsden
2007-04-10 0:06 ` Zachary Amsden
2007-04-10 2:37 ` Chris Wright
2007-04-10 17:03 ` Zachary Amsden
2007-04-10 17:24 ` Chris Wright
2007-04-10 17:24 ` Chris Wright
2007-04-10 21:57 ` Zachary Amsden
2007-04-10 22:16 ` Jeremy Fitzhardinge
2007-04-10 22:16 ` Jeremy Fitzhardinge
2007-04-10 22:28 ` Zachary Amsden [this message]
2007-04-10 22:28 ` Zachary Amsden
2007-04-10 22:38 ` Chris Wright
2007-04-10 22:38 ` Chris Wright
2007-04-10 22:28 ` Chris Wright
2007-04-10 22:28 ` Chris Wright
2007-04-10 22:59 ` Zachary Amsden
2007-04-10 22:59 ` Zachary Amsden
2007-04-12 1:19 ` Zachary Amsden
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=461C0F76.1070308@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 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.