From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: wakeup code translated to .c
Date: Mon, 4 Feb 2008 00:54:43 +0100 [thread overview]
Message-ID: <200802040054.43863.rjw@sisk.pl> (raw)
In-Reply-To: <20080203233313.GF2799@elf.ucw.cz>
On Monday, 4 of February 2008, Pavel Machek wrote:
> On Mon 2008-02-04 00:20:14, Rafael J. Wysocki wrote:
> > On Sunday, 3 of February 2008, Rafael J. Wysocki wrote:
> > > On Sunday, 3 of February 2008, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > > This version works on 32-bit, and builds on 64-bit (but I'm pretty
> > > > > > sure it does not work. 32-bit code probably needs to go into rm/....)
> > > > > >
> > > > >
> > > > > Do you have an updated version or is this the latest one?
> > > >
> > > > I'm glad you ask ;-). Here's reasonably-recent version (I have
> > > > slightly cleaner one, but it got obscured by 2.6.24-git merge), I
> > > > eventually got it to work on 64-bit, by reusing trampoline.S code.
> > >
> > > I needed to rebase it against the current mainline (Makefile conflict).
> > >
> > > Some remarks:
> > >
> > > - It looks like arch/x86/kernel/acpi/wakeup.S is not necessary any more.
> > >
> > > - These warnings:
> > >
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c: In function ???acpi_save_state_mem???:
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:41: warning: initialization makes pointer from integer without a cast
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:50: warning: format ???%d??? expects type ???int???, but argument 2 has type ???long unsigned int???
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:50: warning: format ???%d??? expects type ???int???, but argument 3 has type ???long unsigned int???
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:70: warning: ISO C90 forbids mixed declarations and code
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:82: warning: assignment makes integer from pointer without a cast
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:83: warning: assignment makes integer from pointer without a cast
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:84: warning: ISO C90 forbids mixed declarations and code
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:87: warning: ISO C90 forbids mixed declarations and code
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:90: warning: assignment makes integer from pointer without a cast
> > > /home/rafael/src/linux-2.6/arch/x86/kernel/acpi/sleep.c:91: warning: ISO C90 forbids mixed declarations and code
> > >
> > > look pretty scary.
> >
> > Below is the arch/x86/kernel/acpi/sleep.c part without the warnings (untested).
> >
> > It still contains some hardcoded magic numbers and extern declarations, so
> > I guess the #include list is not complete or another header is necessary.
> >
> > BTW:
> > 1) why exactly is acpi_wakeup_address not (void *)?
>
> Well, it is physical address, not really a pointer.
But then it's converted to a pointer all over the place (same for
acpi_realmode).
Using (void *) will cause it to have the appropriate size and to be type
checked by the compiler in the C code.
> > 2) header->level3_ident_pgt and header->level3_ident_pgt could be
> (char *) IMO
OK
BTW, I don't like the way in which the 'struct wakeup_header' fields are
reproduced in rm/wakeup.S very much, because it makes the code fragile.
It might be better to define the offsets in asm-offsets*.c and refer to them
relative to wakeup_header (if possible).
Rafael
next prev parent reply other threads:[~2008-02-03 23:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 12:01 wakeup code translated to .c Pavel Machek
2008-02-03 17:57 ` Rafael J. Wysocki
2008-02-03 18:16 ` Pavel Machek
2008-02-03 18:24 ` Rafael J. Wysocki
2008-02-03 18:49 ` Sam Ravnborg
2008-02-03 20:02 ` H. Peter Anvin
2008-02-03 22:24 ` Pavel Machek
2008-02-03 22:27 ` Sam Ravnborg
2008-02-04 12:44 ` Pavel Machek
2008-02-03 22:33 ` Rafael J. Wysocki
2008-02-03 23:20 ` Rafael J. Wysocki
2008-02-03 23:30 ` [linux-pm] " Rafael J. Wysocki
2008-02-03 23:33 ` Pavel Machek
2008-02-03 23:54 ` Rafael J. Wysocki [this message]
2008-02-03 23:59 ` Pavel Machek
2008-02-03 23:59 ` Rafael J. Wysocki
2008-02-04 0:05 ` Pavel Machek
2008-02-03 23:56 ` Pavel Machek
2008-02-03 23:57 ` Pavel Machek
2008-02-03 23:57 ` Rafael J. Wysocki
2008-02-04 0:18 ` Pavel Machek
2008-02-03 23:58 ` Pavel Machek
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=200802040054.43863.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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