linux-kernel - Re: [PATCH RFC 0/3] Add guest cpu

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: <503BD920.20603@redhat.com>
Date:	Mon, 27 Aug 2012 13:31:28 -0700
From:	Avi Kivity <avi@...hat.com>
To:	mjw@...ux.vnet.ibm.com
CC:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	peterz@...radead.org, mtosatti@...hat.com, glommer@...allels.com,
	mingo@...hat.com
Subject: Re: [PATCH RFC 0/3] Add guest cpu_entitlement reporting

On 08/27/2012 01:23 PM, Michael Wolf wrote:
> > 
> > How would a guest know what its entitlement is?
> > 
> > 
>
> Currently the Admin/management tool setting up the guests will put it on
> the qemu commandline.  From this it is passed via an ioctl to the host.
> The guest will get the value from the host via a hypercall.
>
> In the future the host could try and do some of it automatically in some
> cases. 

Seems to me it's a meaningless value for the guest.  Suppose it is
migrated to a host that is more powerful, and as a result its relative
entitlement is reduced.  The value needs to be adjusted.

This is best taken care of from the host side.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
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/