From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info.
Date: Tue, 22 Apr 2008 09:16:41 +0000 [thread overview]
Message-ID: <yq04p9ul05i.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <12077165491881-git-send-email-yamahata@valinux.co.jp>
>>>>> "Isaku" = Isaku Yamahata <yamahata@valinux.co.jp> writes:
Isaku> introduce pv_info which describes some randome info about
Isaku> underlying execution environment.
Hi Isaku,
I am missing some of the patches in this series for some reason.
However, I'd like to open the discussion and ask why you are
implementing the pv-ops seperately instead of adding them to the
machine vectors and using the machine vector interface to handle the
direct implementation?
It seems to me that pvops really are just an advanced level of the
ia64 machine vectors and building on top of the interface we already
have would make it easier to support different machine types through
pvops.
Cheers,
Jes
next prev parent reply other threads:[~2008-04-22 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 4:48 [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info Isaku Yamahata
2008-04-22 9:16 ` Jes Sorensen [this message]
2008-04-22 10:02 ` Isaku Yamahata
2008-04-22 10:37 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes Jes Sorensen
2008-04-22 10:41 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info Dong, Eddie
2008-04-22 11:02 ` Isaku Yamahata
2008-04-22 11:30 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes Jes Sorensen
2008-04-22 13:15 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info Dong, Eddie
2008-04-22 13:55 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes Jes Sorensen
2008-04-30 12:29 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info Isaku Yamahata
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=yq04p9ul05i.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-ia64@vger.kernel.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