From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
suspend2-devel@lists.suspend2.net
Subject: Re: x86_64 restore_image declaration needs asmlinkage?
Date: Wed, 28 Jun 2006 13:53:15 +0200 [thread overview]
Message-ID: <200606281353.15252.rjw@sisk.pl> (raw)
In-Reply-To: <200606282048.38746.ncunningham@linuxmail.org>
Hi,
On Wednesday 28 June 2006 12:48, Nigel Cunningham wrote:
> I received a report of problems with CONFIG_REGPARM and suspending, that led
> me to recheck asm calls and declarations. Not being a guru on these things, I
> want to ask advice from those who know more.
>
> Along the way I noticed that current git has:
>
> extern asmlinkage int swsusp_arch_suspend(void);
> extern asmlinkage int swsusp_arch_resume(void);
>
> This is right for x86, but for x86_64, we actually call a C routine in
> arch/x86_64/kernel/suspend.c, which calls restore_image in
> arch/x86_64/kernel/suspend_asm.S. Restore image is declared in suspend.c as
>
> extern int restore_image(void);
>
> should it be:
>
> extern asmlinkage int restore_image(void);
>
> Having swsusp_arch_resume declared as asmlinkage doesn't matter, does it?
No, it doesn't. It would have mattered on i386 if the function had taken any
arguments. AFAICT, on x86_64 it desn't matter at all.
Greetings,
Rafael
next prev parent reply other threads:[~2006-06-28 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 10:48 x86_64 restore_image declaration needs asmlinkage? Nigel Cunningham
2006-06-28 11:53 ` Rafael J. Wysocki [this message]
2006-06-28 12:00 ` Nigel Cunningham
2006-06-28 12:10 ` 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=200606281353.15252.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=ncunningham@linuxmail.org \
--cc=suspend2-devel@lists.suspend2.net \
/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