--- a/arch/i386/xen/time.c
+++ b/arch/i386/xen/time.c
@@ -105,17 +105,15 @@ static void get_runstate_snapshot(struct
preempt_enable();
}
-static void setup_runstate_info(void)
+static void setup_runstate_info(int cpu)
{
struct vcpu_register_runstate_memory_area area;
-
On Wednesday 06 June 2007 12:05:22 Jeremy Fitzhardinge wrote:
Jan Beulich wrote:
Xen itself knows to deal with this (by using an error correction factor to
slow down the local [TSC-based] clock), but for the kernel such a situation
may be fatal: If clocksource-cycle_last was most recently
On 6/6/07 12:00, Jan Beulich [EMAIL PROTECTED] wrote:
If the error across CPUS is +/- just a few microseconds at worst then having
the clocksource clamp to no less than the last timestamp returned seems a
reasonable fix. Time won't 'stop' for longer than the cross-CPU error, and
that
Andi Kleen [EMAIL PROTECTED] 06.06.07 14:18
Yes, this could be an issue. Is there any way to get an interrupt or MCE
when thermal throttling occurs?
Yes you can get an thermal interrupt from the local APIC. See the Linux
kernel source. Of course there would be still a race window.
On the
On Wednesday 06 June 2007 14:46:59 Jan Beulich wrote:
Andi Kleen [EMAIL PROTECTED] 06.06.07 14:18
Yes, this could be an issue. Is there any way to get an interrupt or MCE
when thermal throttling occurs?
Yes you can get an thermal interrupt from the local APIC. See the Linux
kernel
Somehow an smp_processor_id() survived the transition to passing the
cpu around.
Signed-off-by: Jeremy Fitzhardinge [EMAIL PROTECTED]
Cc: Jan Beulich [EMAIL PROTECTED]
---
arch/i386/xen/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This series:
1. Updates the boot protocol to version 2.07
2. Clean up the existing build process, to get rid of tools/build and
make the linker do more heavy lifting
3. Make the bzImage payload an ELF file. The bootloader can extract
this as a naked ELF file by skipping over
Proposed updates for version 2.07 of the boot protocol. This includes:
load_flags.KEEP_SEGMENTS- flag to request/inhibit segment reloads
hardware_subarch- what subarchitecture we're booting under
hardware_subarch_data - per-architecture data
kernel_payload - address of the raw
Signed-off-by: Jeremy Fitzhardinge [EMAIL PROTECTED]
Cc: Vivek Goyal [EMAIL PROTECTED]
---
include/linux/elf_boot.h | 15 +++
1 file changed, 15 insertions(+)
===
--- /dev/null
+++ b/include/linux/elf_boot.h
@@ -0,0
Jeremy Fitzhardinge wrote:
This patch makes the payload of the bzImage file an ELF file. In
other words, the bzImage is structured as follows:
- boot sector
- 16bit setup code
- ELF header
- decompressor
- compressed kernel
A bootloader may find the start of the ELF file by
H. Peter Anvin wrote:
I was thinking prescriptive, having the decompressor read the output
stream and interpret it as ELF. I guess a descriptive approach could be
made to work, too (I haven't really thought about that avenue of
approach), but the prescriptive model seems more powerful, at
H. Peter Anvin wrote:
It doesn't if we simply declare that a certain chunk of memory is
available to it, for the case where it runs in the native configuration.
Since it doesn't have to support *any* ELF file, just the kernel one,
that's an option.
I suppose. But given that its always
On Wednesday 06 June 2007 7:41 pm, H. Peter Anvin wrote:
This makes vmlinux (normally stripped) recoverable from the bzImage file
and so anything that is currently booting vmlinux would be serviced by
this scheme.
Would this make it sane to strip the initramfs image out of vmlinux with
Rob Landley wrote:
On Wednesday 06 June 2007 7:41 pm, H. Peter Anvin wrote:
This makes vmlinux (normally stripped) recoverable from the bzImage file
and so anything that is currently booting vmlinux would be serviced by
this scheme.
Would this make it sane to strip the initramfs image out
14 matches
Mail list logo
