search for: ffh

This patchset enable support for C1 mwait entry. [PATCH 1/3] dom0-C1-FFH.patch. It gets C1 information from ACPI table and pass it to Xen. [PATCH 2/3] add-idx-field.patch. This patch adds an idx field in the ''struct acpi_processor_cx''. It can simplify some coding lines. [PATCH 3/3] xen-C1-FFH.patch. It adds support for C1 FFH (mwait) entry. Meanwhile a...

Using Xen 4.2 unstable rev. 25483. I get errors like this: pt_pci_read_config: [00:10:0] Error: Failed to read register with offset exceeding FFh. [Offset:ffh][Length:1] in my qemu log for a domU with some devices passed through to it. I investigated and found that at hw/pass-through.c line 1717 (http://xenbits.xen.org/gitweb/?p=qemu-xen-unstable.git;a=blob;f=hw/pass-through.c;h=8581253bc86391d6e348e02464f9ed5d2e579a0d;hb=HEAD#l1717) the c...

# HG changeset patch # User Boris Ostrovsky <boris.ostrovsky@amd.com> # Date 1330642361 -3600 # Node ID 99df5c6b2964ceaa73651d7bc02fb1ae820f7691 # Parent a7bacdc5449a2f7bb9c35b2a1334b463fe9f29a9 x86: Use deep C states for off-lined CPUs Currently when a core is taken off-line it is placed in C1 state (unless MONITOR/MWAIT is used). This patch allows a core to go to deeper C states

Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan

...b/arch/x86/kernel/acpi/processor.c index 8c9526d..d88866c 100644 --- a/arch/x86/kernel/acpi/processor.c +++ b/arch/x86/kernel/acpi/processor.c @@ -60,7 +60,7 @@ static void init_intel_pdc(struct acpi_processor *pr, struct cpuinfo_x86 *c) /* * If mwait/monitor is unsupported, C2/C3_FFH will be disabled */ - if (!cpu_has(c, X86_FEATURE_MWAIT)) + if (!cpu_has(c, X86_FEATURE_MWAIT) && !xen_initial_domain()) buf[2] &= ~(ACPI_PDC_C_C2C3_FFH); obj->type = ACPI_TYPE_BUFFER; Above trick is ugly and error-prone, since it alway...

Is there something that I can put on a drive's boot sector so that when booted it just reboots, and that its partition information is also intact? My application need is stateless computing. The OS loads over the network with the help of pxelinux.0, but when 1000s of nodes reboot in parallel a few fail to boot. When PXE fails it boots the next device--in most cases this is the local HD.

Whilst looking at the 3.61 isolinux.asm file I noticed that the code uses a spec buffer size of 13h for the initial BIOS call with the drive number passed in in DL. It then uses a spec buffer size of 13 when scanning drive numbers from FFh to 81h Line 291 is mov byte [spec_packet],13h Lines 576 to 577 are mov si,spec_packet mov byte [si],13 ; Size of buffer Is the use of 13 an error or is there some reason I don't understand ?

Current xen-linux (2.6.18) not include support for Cx MWAIT entry method. Back port from latest Linux kernel (already there since 2.6.23). Without this patch, _CST method couldn''t get C states with FFH address space type. Signed-off-by: Wei Gang <gang.wei@intel.com> Jimmy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...* byte 2 is input voltage * byte 3 is output voltage * byte 4 is input frequency * byte 5 is Version IMP is FFH * byte 6 is output frequency * byte 7 is XX...

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

...-------- I added 4 data fields to the patch_area struct that is set up for the memdisk TSR. 1. the BIOS_EQUIP word from the BIOS Data Area 2. the BIOS_HD_COUNT byte from the BIOS Data Area 3. a copy of the first 128 interrupt vectors (0-7Fh) 4. a checksum on the upper 128 interrupt vectors (80h-FFh) to validate that they are unchanged when we later execute our *restore* procedure. The BIOS_EQUIP and BIOS_HD_COUNT values are saved because one of them is modified as part of the memdisk installation. My testing shows that the highest interrupt vector that is being used is 77h ... for IDE disk...