linux-kernel - [RFC] follow-on patches to acpi processor and cpufreq harvester^H^H^Hpassthru (v4).

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1329782868-1696-1-git-send-email-konrad.wilk@oracle.com>
Date:	Mon, 20 Feb 2012 19:07:45 -0500
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	pasik@....fi
Cc:	xen-devel@...ts.xensource.com, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, JBeulich@...ell.com,
	kevin.tian@...el.com, ke.yu@...el.com
Subject: [RFC] follow-on patches to acpi processor and cpufreq harvester^H^H^Hpassthru (v4).

I decided that passthru sounded much better so:
 [PATCH 1/3] xen/processor-passthru: Change the name to passthru

does the move to the new name, and then the next one implements the dom0_max_vcpu
support:
 [PATCH 2/3] xen/processor-passthru: Support vCPU != pCPU - aka

by enumerating the ACPI processor values directly and re-using the 'struct acpi_processor'
for the rest (the ones not enumerated by ACPI layer). I chatted with the Intel folks and
they said that it is safe to assume that the _PXX and _CXX values are the same across
all the CPUs. Not entirely sure about AMD so I need to chat with them.

The last one is just an fixup to make it easier to read:
 [PATCH 3/3] xen/processor-passthru: Remove the print_hex_dump - as

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/