[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 5/5] xen: Write CR0, CR3 and CR4 in arch_set_info_guest()
- To: Jan Beulich <JBeulich@xxxxxxxx>
- From: Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx>
- Date: Tue, 19 May 2015 12:45:48 +0200
- Cc: Tim Deegan <tim@xxxxxxx>, Kevin Tian <kevin.tian@xxxxxxxxx>, "wei.liu2@xxxxxxxxxx" <wei.liu2@xxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>, Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Eddie Dong <eddie.dong@xxxxxxxxx>, "Aravind.Gopalakrishnan@xxxxxxx" <Aravind.Gopalakrishnan@xxxxxxx>, "suravee.suthikulpanit@xxxxxxx" <suravee.suthikulpanit@xxxxxxx>, Keir Fraser <keir@xxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
- Delivery-date: Tue, 19 May 2015 10:46:08 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Tue, May 19, 2015 at 12:31 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>> On 19.05.15 at 12:14, <tamas.lengyel@xxxxxxxxxxxx> wrote:
>> You can have a response flag for it to tell Xen to look at the
>> new_value. What I meant is why restrict the feature to be DENY only.
>> You might as well let the user choose the value he wants to see in the
>> register.
>
> Hmm, I don't think allowing the use to chose arbitrary values here
> is going to be the right direction.
>
> Jan
(This time adding xen-devel)
Care to elaborate why it would be a problem? The user would still have
to have knowledge about what value he sets the register as an
"arbitrary" value will crash the system most probably.
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
