Hi Juergen,
On 03/02/2018 05:25 PM, Juergen Gross wrote:
On 02/03/18 18:09, Andrew Cooper wrote:
On 02/03/18 17:05, Juergen Gross wrote:
On 02/03/18 17:51, Jan Beulich wrote:
On 02.03.18 at 17:25, wrote:
On 02/03/18 16:18, Jan Beulich wrote:
On 02.03.18 at 17:04, wrote:
The proper way to
Hi Andrew,
On 03/02/2018 05:09 PM, Andrew Cooper wrote:
On 02/03/18 17:05, Juergen Gross wrote:
On 02/03/18 17:51, Jan Beulich wrote:
On 02.03.18 at 17:25, wrote:
On 02/03/18 16:18, Jan Beulich wrote:
On 02.03.18 at 17:04, wrote:
The proper way to do this is indeed by a nominated (guest)
On 02/03/18 18:09, Andrew Cooper wrote:
> On 02/03/18 17:05, Juergen Gross wrote:
>> On 02/03/18 17:51, Jan Beulich wrote:
>> On 02.03.18 at 17:25, wrote:
On 02/03/18 16:18, Jan Beulich wrote:
On 02.03.18 at 17:04, wrote:
>> The proper way to do this is indeed by a nominated
On 02/03/18 17:05, Juergen Gross wrote:
> On 02/03/18 17:51, Jan Beulich wrote:
> On 02.03.18 at 17:25, wrote:
>>> On 02/03/18 16:18, Jan Beulich wrote:
>>> On 02.03.18 at 17:04, wrote:
> The proper way to do this is indeed by a nominated (guest) physical
> address, at which point
On 02/03/18 17:51, Jan Beulich wrote:
On 02.03.18 at 17:25, wrote:
>> On 02/03/18 16:18, Jan Beulich wrote:
>> On 02.03.18 at 17:04, wrote:
The proper way to do this is indeed by a nominated (guest) physical
address, at which point Xen can make all/any updates at times of its
>
On 02/03/18 17:25, Julien Grall wrote:
>
>
> On 02/03/18 16:18, Jan Beulich wrote:
> On 02.03.18 at 17:04, wrote:
>>> The proper way to do this is indeed by a nominated (guest) physical
>>> address, at which point Xen can make all/any updates at times of its
>>> choosing, and the guests page
>>> On 02.03.18 at 17:25, wrote:
> On 02/03/18 16:18, Jan Beulich wrote:
> On 02.03.18 at 17:04, wrote:
>>> The proper way to do this is indeed by a nominated (guest) physical
>>> address, at which point Xen can make all/any updates at times of its
>>> choosing, and the guests pagetable/permi
On 02/03/18 16:18, Jan Beulich wrote:
On 02.03.18 at 17:04, wrote:
The proper way to do this is indeed by a nominated (guest) physical
address, at which point Xen can make all/any updates at times of its
choosing, and the guests pagetable/permissions state at an instantaneous
moment don't mat
On 02/03/18 16:18, Jan Beulich wrote:
On 02.03.18 at 17:04, wrote:
>> The proper way to do this is indeed by a nominated (guest) physical
>> address, at which point Xen can make all/any updates at times of its
>> choosing, and the guests pagetable/permissions state at an instantaneous
>> mome
>>> On 02.03.18 at 17:04, wrote:
> The proper way to do this is indeed by a nominated (guest) physical
> address, at which point Xen can make all/any updates at times of its
> choosing, and the guests pagetable/permissions state at an instantaneous
> moment don't matter.
>
> If you've got time to
On 02/03/18 15:57, Julien Grall wrote:
> Hi,
>
> While I was looking at some unrelated problem with Xen ARM P2M code, I
> noticed that the function update_runstate_area is using guest virtual
> address to update the vCPU runstate. That function will be called when
> context switch to a vCPU. Howeve
Hi,
While I was looking at some unrelated problem with Xen ARM P2M code, I
noticed that the function update_runstate_area is using guest virtual
address to update the vCPU runstate. That function will be called when
context switch to a vCPU. However, that vCPU may run in userspace
context. Wh
12 matches
Mail list logo
