All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kip.macy@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.comIan Pratt <Ian.Pratt@cl.cam.ac.uk>,
	Scott Parish <srparish@us.ibm.com>,
	Gerd Knorr <kraxel@bytesex.org>
Subject: Re: understanding __linear_l2_table and friends
Date: Fri, 22 Apr 2005 13:47:34 -0700	[thread overview]
Message-ID: <b1fa291705042213476eb46d7c@mail.gmail.com> (raw)
In-Reply-To: <20050422110425.GW7715@wotan.suse.de>

> 
> Since PAE is a temporary crock I would chose the least intrusive
> variant to the codebase :)
> 
A temporary crock that is likely to be 80% of Xen's deployments for
the next couple of years.

       -Kip

  reply	other threads:[~2005-04-22 20:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 13:51 understanding __linear_l2_table and friends Ian Pratt
2005-04-21 19:42 ` Gerd Knorr
2005-04-22 11:04 ` Andi Kleen
2005-04-22 20:47   ` Kip Macy [this message]
2005-04-23 15:08     ` Andi Kleen
2005-04-23 15:13       ` Wim Coekaerts
2005-04-23 15:28         ` Andi Kleen
2005-04-24 19:55           ` Gerd Knorr
2005-04-25  0:41             ` David Hopwood
2005-04-25  0:46               ` Mark Williamson
2005-04-25  2:53                 ` David Hopwood
2005-04-23 15:20 ` understanding __linear_l2_table and friends II Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-04-21 21:13 understanding __linear_l2_table and friends Ian Pratt
2005-04-20 20:27 Ian Pratt
2005-04-20 21:38 ` Gerd Knorr
2005-04-20 22:10   ` Ian Pratt
2005-04-20 18:53 Ian Pratt
2005-04-20 19:14 ` Gerd Knorr
2005-04-20 16:25 Ian Pratt
2005-04-20 16:31 ` Keir Fraser
2005-04-19 23:03 Scott Parish
2005-04-20 10:05 ` Keir Fraser
2005-04-20 16:06   ` Gerd Knorr
2005-04-20 19:46   ` Scott Parish

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=b1fa291705042213476eb46d7c@mail.gmail.com \
    --to=kip.macy@gmail.com \
    --cc=ak@suse.de \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.comIan \
    /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.