All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: [patch/unstable] page table cleanups
Date: Mon, 14 Mar 2005 14:36:10 +0100	[thread overview]
Message-ID: <20050314133610.GA13023@bytesex> (raw)
In-Reply-To: <b711afc6bbba710e1a80c888dd89960e@cl.cam.ac.uk>

  Hi,

> The other is to change those unsigned longs into a physaddr_t which is
> u64 on 32-bit PAE systems.

I've considered doing something like that as well, but I don't think
that this is a good idea.

> I'm not fussed too much which way we go, but Ian has pointed out that
> the l*_pgentry_t types haven't actually found us any bugs (although I
> might argue that it has prevented any bugs ever getting as far as the
> master repository :-) ).

I'd argue that way as well.  The whole point of the "typedef { u{32|64}
l? } l?_pgentry_t" types and the access macros is to make the _compiler_
notice bugs, so they can't creep into the code base in the first place
because gcc refuses to compile the buggy code ;)

cheers,

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-14 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 12:07 [patch/unstable] page table cleanups Gerd Knorr
2005-03-14 12:49 ` Keir Fraser
2005-03-14 13:36   ` Gerd Knorr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-14 14:00 Ian Pratt
2005-03-14 15:14 ` Gerd Knorr

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=20050314133610.GA13023@bytesex \
    --to=kraxel@bytesex.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.