Hi Julien,
On 11/03/2022 18:34, Julien Grall wrote:
Hi,
On 10/03/2022 17:45, Ayan Kumar Halder wrote:
When the data abort is caused due to cache maintenance for an address,
there are three scenarios:-
1. Address belonging to a non emulated region - For this, Xen should
set the corresponding
Hi,
On 11/03/2022 13:21, Ayan Kumar Halder wrote:
enum io_state try_handle_mmio(struct cpu_user_regs *regs,
mmio_info_t *info)
{
struct vcpu *v = current;
const struct mmio_handler *handler = NULL;
int rc;
ASSERT(info->dabt.ec ==
Hi,
On 10/03/2022 17:45, Ayan Kumar Halder wrote:
When the data abort is caused due to cache maintenance for an address,
there are three scenarios:-
1. Address belonging to a non emulated region - For this, Xen should
set the corresponding bit in the translation table entry to valid and
return
Hi Stefano,
On 11/03/2022 02:25, Stefano Stabellini wrote:
On Thu, 10 Mar 2022, Ayan Kumar Halder wrote:
When the data abort is caused due to cache maintenance for an address,
there are three scenarios:-
1. Address belonging to a non emulated region - For this, Xen should
set the
On Thu, 10 Mar 2022, Ayan Kumar Halder wrote:
> When the data abort is caused due to cache maintenance for an address,
> there are three scenarios:-
>
> 1. Address belonging to a non emulated region - For this, Xen should
> set the corresponding bit in the translation table entry to valid and
>
When the data abort is caused due to cache maintenance for an address,
there are three scenarios:-
1. Address belonging to a non emulated region - For this, Xen should
set the corresponding bit in the translation table entry to valid and
return to the guest to retry the instruction. This can
