From: Yuhong Bao <yuhongbao_386@hotmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"sonnyrao@chromium.org" <sonnyrao@chromium.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu>
Subject: RE: IO regression after ab8fabd46f on x86 kernels with high memory
Date: Sun, 2 Jun 2013 18:17:51 -0700 [thread overview]
Message-ID: <BLU177-W3672A7BA58CC4EE16F4EEAC39D0@phx.gbl> (raw)
In-Reply-To: <518AA321.6070900@zytor.com>
> We kernel guys have been asking the distros to ship 64-bit kernels even
> in their 32-bit distros for many years, but concerns of compat issues
> and the desire to deprecate 32-bit userspace seems to have kept that
> from happening.
And now there is another reason: to call 64-bit EFI runtime services.
In retrospect, I would have stuck with 32-bit EFI with 64-bit kernels calling runtime services in compatibility mode, but of course it is too late for that now.
Yuhong Bao
prev parent reply other threads:[~2013-06-03 1:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:44 Pierre-Loup A. Griffais
2013-04-27 1:53 ` Rik van Riel
2013-04-27 2:42 ` Johannes Weiner
2013-04-29 21:53 ` Pierre-Loup A. Griffais
2013-04-29 22:03 ` Linus Torvalds
2013-04-29 22:08 ` Pierre-Loup A. Griffais
2013-05-02 4:37 ` Sonny Rao
2013-04-30 0:48 ` Rik van Riel
2013-04-30 1:06 ` Pierre-Loup A. Griffais
2013-05-02 1:34 ` Steven Rostedt
2013-05-02 2:46 ` [PATCH] mm,x86: limit 32 bit kernel to 12GB memory Rik van Riel
2013-05-02 7:37 ` Pierre-Loup A. Griffais
2013-05-02 20:03 ` Linus Torvalds
2013-05-11 9:16 ` Yuhong Bao
2013-05-08 19:10 ` IO regression after ab8fabd46f on x86 kernels with high memory H. Peter Anvin
2013-06-03 1:17 ` Yuhong Bao [this message]
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=BLU177-W3672A7BA58CC4EE16F4EEAC39D0@phx.gbl \
--to=yuhongbao_386@hotmail.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=kamezawa.hiroyu@jp.fujitsu \
--cc=linux-kernel@vger.kernel.org \
--cc=pgriffais@valvesoftware.com \
--cc=riel@redhat.com \
--cc=sonnyrao@chromium.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®