From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH] xen/x86: Be more power-efficient when waiting forever
Date: Mon, 2 Dec 2013 14:38:09 +0000 [thread overview]
Message-ID: <1385995089-440-1-git-send-email-andrew.cooper3@citrix.com> (raw)
The effect is unchanged, but the processor will be spending most of its time
in the C1 or C1E power state rather than C0.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
CC: George Dunlap <george.dunlap@eu.citrix.com>
---
This was discovered while I was playing about in the early_page_fault()
handler with the IBM box which was corruption the Xen code section.
There is one final for(;;); loop, but is in common code and immediately
following a call to panic(), so is actually dead code and will be cleaned up
in v2 of my "noreturn" series at the start of 4.5
George: I am requesting that this get a freeze exception, under the
qualification of #2 "An awesome release", given no function change threatening
---
xen/arch/x86/efi/boot.c | 3 ++-
xen/arch/x86/traps.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/efi/boot.c b/xen/arch/x86/efi/boot.c
index 0dd935c..602cc12 100644
--- a/xen/arch/x86/efi/boot.c
+++ b/xen/arch/x86/efi/boot.c
@@ -201,7 +201,8 @@ static void __init __attribute__((__noreturn__)) blexit(const CHAR16 *str)
efi_bs->FreePages(xsm.addr, PFN_UP(xsm.size));
efi_bs->Exit(efi_ih, EFI_SUCCESS, 0, NULL);
- for( ; ; ); /* not reached */
+ for ( ; ; ) /* not reached */
+ halt();
}
/* generic routine for printing error messages */
diff --git a/xen/arch/x86/traps.c b/xen/arch/x86/traps.c
index d8b3eac..8c355e5 100644
--- a/xen/arch/x86/traps.c
+++ b/xen/arch/x86/traps.c
@@ -1448,7 +1448,8 @@ void __init do_early_page_fault(struct cpu_user_regs *regs)
printk("Stack dump: ");
while ( ((long)stk & ((PAGE_SIZE - 1) & ~(BYTES_PER_LONG - 1))) != 0 )
printk("%p ", _p(*stk++));
- for ( ; ; ) ;
+ for ( ; ; )
+ halt();
}
}
--
1.7.10.4
next reply other threads:[~2013-12-02 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 14:38 Andrew Cooper [this message]
2013-12-02 15:03 ` [PATCH] xen/x86: Be more power-efficient when waiting forever Jan Beulich
2013-12-02 15:06 ` Andrew Cooper
2013-12-02 15:23 ` Keir Fraser
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=1385995089-440-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).