qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume
Date: Sat, 15 Jan 2005 12:48:54 +0100	[thread overview]
Message-ID: <41E90326.2020901@bellard.org> (raw)
In-Reply-To: <20050115012120.GA4743@hugang.soulinfo.com>

hugang@soulinfo.com wrote:
> On Sat, Jan 15, 2005 at 12:42:35AM +0100, Rafael J. Wysocki wrote:
> 
>>On Friday, 14 of January 2005 15:34, you wrote:
>>
>>>On Thu, Jan 13, 2005 at 07:09:24PM +0100, Rafael J. Wysocki wrote:
>>>
>>>>Hi,
>>>>
>>>>
>>>>Has this patch been ported to x86_64?  Or is there a newer version of it anywhere,
>>>>or an alternative?
>>>>
>>>
>>>Ok, Here is a new patch with x86_64 support, But I have not machine, So
>>>Need someone test it. 
>>>
>>>2.6.11-rc1-mm1 
>>> -> 2005-1-14.core.diff 	core patch		TEST PASSED
>>>  -> 2005-1-14.x86_64.diff	x86_64 patch	NOT TESTED
>>
>>Unfortunately, on x86_64 it goes south on suspend, probably somwhere in write_pagedir(),
>>but I'm not quite sure as I can't make it print any useful stuff to the serial console
>>(everything is dumped to a virtual tty only).  Seemingly, it prints some
>>"write_pagedir: ..." debug messages and then starts to print garbage in
>>an infinite loop.
> 
> 
> Try enable debug in swsusp, 
> <....>
> #include "power.h"
> #undef pr_debug
> #define pr_debug printk
> <....>
> 
>  Enable serial conosole, 
>  Adding console=ttyS0 in boot command line.
> 
> Then do software suspend, And send the log to me, that will useful. 
> 
> For other reference, I using qemu As X86-64 emulation, But current qemu
> X86-64 not full works, the kernel hang after copy_page in suspend, I'll
> enable CPU and ASM log in qemu to finger other where is the problem.

I recently made a fix in fxsave/fxrestor which may correct some issues 
on x86_64. Strangely, the CVS commit mail did not appear on the mailing 
list...

The state of x86_64 is that the install of Fedora core 3 for x86_64 
begins to work (you can select the language for example), but there are 
some invalid characters displayed on screen. I believe there is a sign 
extension problem in a 64 bit instruction.

Now that SSE and MMX are implemented, no feature is lacking in the QEMU 
x86_64 emulation... "just" a problem of debugging now :-)

I did not enable SSE and MMX for x86 because I fear there are still bugs 
which may cause regressions. Interested people can enable the line:

--
      env->cpuid_features |= CPUID_FXSR | CPUID_MMX | CPUID_SSE | 
CPUID_SSE2 | CPUID_PAE;
--

and see if their OS and application still work.

Fabrice.

  reply	other threads:[~2005-01-15 12:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0412241434110.17285@ppc970.osdl.org>
     [not found] ` <200501131909.26021.rjw@sisk.pl>
     [not found]   ` <20050114143400.GA27657@hugang.soulinfo.com>
     [not found]     ` <200501150042.35377.rjw@sisk.pl>
2005-01-15  1:21       ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) hugang
2005-01-15 11:48         ` Fabrice Bellard [this message]
2005-01-15 16:40           ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume hugang
2005-01-16  4:38             ` hugang
2005-01-15 18:02           ` [Qemu-devel] W2K SP0 Status (was: Re: 2.6.10-mm3: swsusp: out of memory on resume) Tim
2005-01-17 18:02           ` [Qemu-devel] Re: Re: 2.6.10-mm3: swsusp: out of memory on resume Ronald
2005-01-17 21:54             ` Fabrice Bellard
2005-01-22  4:17               ` [Qemu-devel] " Anand Kumria
2005-01-22 12:42                 ` Johannes Schindelin
     [not found]         ` <200501151147.32919.rjw@sisk.pl>
     [not found]           ` <200501152220.42129.rjw@sisk.pl>
2005-01-16  5:54             ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) hugang
2005-01-16 10:07               ` Rafael J. Wysocki

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=41E90326.2020901@bellard.org \
    --to=fabrice@bellard.org \
    --cc=qemu-devel@nongnu.org \
    --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;
as well as URLs for NNTP newsgroup(s).