On Jan 16, 2008, at 9:12 PM, Dan Kenigsberg wrote:
> On Wed, Jan 16, 2008 at 06:34:08PM +0100, Alexander Graf wrote:
>> Dan Kenigsberg wrote:
>>> On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
>>>
Dan Kenigsberg wrote:
> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Ale
On Wed, Jan 16, 2008 at 06:34:08PM +0100, Alexander Graf wrote:
> Dan Kenigsberg wrote:
> > On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
> >
> >> Dan Kenigsberg wrote:
> >>
> >>> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
> >>>
> >>>
>
Dan Kenigsberg wrote:
> On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
>
>> Dan Kenigsberg wrote:
>>
>>> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
>>>
>>>
Hi,
Currently CPUID function 4 is broken. This function's values rely on
On Tue, Jan 15, 2008 at 08:57:45AM +0100, Alexander Graf wrote:
> Dan Kenigsberg wrote:
> > On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
> >
> >> Hi,
> >>
> >> Currently CPUID function 4 is broken. This function's values rely on the
> >> value of ECX.
> >> To solve the issue c
Dan Kenigsberg wrote:
> On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
>
>> Hi,
>>
>> Currently CPUID function 4 is broken. This function's values rely on the
>> value of ECX.
>> To solve the issue cleanly, there is already a new API for cpuid
>> settings, which is not used yet.
On Mon, Jan 14, 2008 at 02:49:31PM +0100, Alexander Graf wrote:
> Hi,
>
> Currently CPUID function 4 is broken. This function's values rely on the
> value of ECX.
> To solve the issue cleanly, there is already a new API for cpuid
> settings, which is not used yet.
> Using the current interface, th
Hi,
Currently CPUID function 4 is broken. This function's values rely on the
value of ECX.
To solve the issue cleanly, there is already a new API for cpuid
settings, which is not used yet.
Using the current interface, the function 4 can be easily passed
through, by giving multiple function 4 outpu