public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	Jens Axboe <axboe@kernel.dk>,
	Sreenivas.Bagalkote@lsil.com, Sumant.Patro@lsil.com,
	jeff@garzik.org, lkml <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: megaraid_sas suspend ok, resume oops
Date: Sat, 2 Sep 2006 16:10:01 -0400	[thread overview]
Message-ID: <20060902201001.GC30379@redhat.com> (raw)
In-Reply-To: <200609022147.05503.rjw@sisk.pl>

On Sat, Sep 02, 2006 at 09:47:05PM +0200, Rafael J. Wysocki wrote:

 > > Precluding NX support + swsusp kinda sucks, but I guess it's a tiny subset of users.
 > 
 > Well, I think the majority of NX-capable CPUs are also x86_64, in which case
 > I'd recommend using a 64-bit kernel anyway.

There's a fairly large number of these "Core Duo" systems out there :)
Hopefully these are the last CPUs lacking longmode that Intel will make.
Asides from these, the only other 32-bit only CPUs with NX are the newer VIA C3s.

For the Fedora users it's not that big a deal not being able to take advantage
of NX, as we fall back to using the old segment limit tricks that exec-shield
does to emulate NX, without having to worry about PAE headaches.

Given the only other use of PAE is >4GB support, and these systems typically
max out at 4GB due to the limited number of memory slots, it's not really that
big a problem.

 > I was afraid the issue would be urgent, but it doesn't seem so now.  I'd like to
 > postpone fixing it until we can create suspend images larger that 350 meg on
 > i386 boxes with highmem (the patch is ready to go to -mm after 2.6.19-rc1 as
 > 2.6.20 material).

Sounds good to me.

		Dave

-- 
http://www.codemonkey.org.uk

-- 
VGER BF report: H 0.178966

      reply	other threads:[~2006-09-02 20:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 17:04 megaraid_sas suspend ok, resume oops Jeff Chua
2006-08-28 21:55 ` Pavel Machek
2006-08-29  8:15 ` Jens Axboe
2006-08-29 12:22   ` Jeff Chua
2006-08-29 20:39     ` Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops) Pavel Machek
2006-08-31 17:05       ` Rafael J. Wysocki
2006-08-29 23:45     ` megaraid_sas suspend ok, resume oops Nigel Cunningham
2006-08-30  1:45       ` Jeff Chua
2006-08-30  2:30         ` Nigel Cunningham
2006-08-30  8:41           ` Jeff Chua
2006-08-30  8:54       ` Rafael J. Wysocki
2006-09-02 13:30         ` Dave Jones
2006-09-02 19:47           ` Rafael J. Wysocki
2006-09-02 20:10             ` Dave Jones [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=20060902201001.GC30379@redhat.com \
    --to=davej@redhat.com \
    --cc=Sreenivas.Bagalkote@lsil.com \
    --cc=Sumant.Patro@lsil.com \
    --cc=axboe@kernel.dk \
    --cc=jeff.chua.linux@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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