All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 00/15] ia64/pv_ops take 5
Date: Mon, 19 May 2008 07:46:14 +0000	[thread overview]
Message-ID: <48313046.6030602@goop.org> (raw)
In-Reply-To: <12095585682308-git-send-email-yamahata@valinux.co.jp>

Isaku Yamahata wrote:
> Yes, I also really want such a tool and I've thought of it.
> I want to prevent people from accidently breaking paravirtualization
> and only a way to do so would be by enforcing.
> I think it can be easily achived by CPP macro trick.
> At worst a simple .s (or .o) parser.
>   

For what its worth, this hasn't been a problem on x86 at all.  All the 
"interesting" instructions are used via macros/inline functions, and 
there have been no instances (that I know of, at least) of naked ones 
appearing anywhere.  And all the gatekeeper maintainers are definitely 
aware of the paravirt constraints, so I don't think any would make it 
past review.

    J

  parent reply	other threads:[~2008-05-19  7:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 12:29 [PATCH 00/15] ia64/pv_ops take 5 Isaku Yamahata
2008-04-30 12:29 ` [PATCH 01/15] ia64: preparation: remove extern in irq_ia64.c Isaku Yamahata
2008-04-30 12:29 ` [PATCH 02/15] ia64/pv_ops: preparation: introduce ia64_set_rr0_to_rr4() to make kernel paravirtualization friendly Isaku Yamahata
2008-04-30 12:29 ` [PATCH 03/15] ia64/pv_ops: preparation: introduce ia64_get_psr_i() " Isaku Yamahata
2008-04-30 12:29 ` [PATCH 04/15] ia64/pv_ops: introduce pv_info which describes some random info Isaku Yamahata
2008-04-30 12:29 ` [PATCH 05/15] ia64/pv_ops: introduce pv_cpu_ops to paravirtualize privileged instructions Isaku Yamahata
2008-04-30 12:29 ` [PATCH 06/15] ia64/pv_ops: preparation for paravirtulization of hand written assembly code Isaku Yamahata
2008-04-30 12:29 ` [PATCH 07/15] ia64/pv_ops: define paravirtualized instructions for native Isaku Yamahata
2008-04-30 12:29 ` [PATCH 08/15] ia64/pv_ops: paravirtualize minstate.h Isaku Yamahata
2008-04-30 12:29 ` [PATCH 09/15] ia64/pv_ops: paravirtualize ivt.S Isaku Yamahata
2008-04-30 12:29 ` [PATCH 10/15] ia64/pv_ops: paravirtualize entry.S Isaku Yamahata
2008-04-30 12:29 ` [PATCH 11/15] ia64/pv_ops: paravirtualize NR_IRQS Isaku Yamahata
2008-04-30 12:29 ` [PATCH 12/15] ia64/pv_ops: define initialization hooks, pv_init_ops, for paravirtualized environment Isaku Yamahata
2008-04-30 12:29 ` [PATCH 13/15] ia64/pv_ops: add hooks, pv_iosapic_ops, to paravirtualize iosapic Isaku Yamahata
2008-04-30 12:29 ` [PATCH 14/15] ia64/pv_ops: add hooks, pv_irq_ops, to paravirtualized irq related operations Isaku Yamahata
2008-04-30 12:29 ` [PATCH 15/15] ia64/pv_ops: add to hooks, pv_time_ops, for steal time accounting Isaku Yamahata
2008-05-07  2:38 ` [PATCH 00/15] ia64/pv_ops take 5 Isaku Yamahata
2008-05-07  2:38 ` Isaku Yamahata
2008-05-17  0:06 ` Luck, Tony
2008-05-17  0:06 ` Luck, Tony
2008-05-19  1:52   ` Isaku Yamahata
2008-05-19  1:52 ` Isaku Yamahata
2008-05-19  7:46   ` Jeremy Fitzhardinge
2008-05-21  2:38   ` [Xen-ia64-devel] " Akio Takebe
2008-05-19  7:46 ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-30 12:29 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=48313046.6030602@goop.org \
    --to=jeremy@goop.org \
    --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 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.