|
From: | yangxiaojuan |
Subject: | Re: [PATCH v3 34/43] hw/intc: Add LoongArch extioi interrupt controller(EIOINTC) |
Date: | Fri, 13 May 2022 16:27:46 +0800 |
User-agent: | Mozilla/5.0 (X11; Linux loongarch64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 |
On 5/9/22 04:38, yangxiaojuan wrote:Could we use the bitmapping as the default cpu or ip map format? Becaue we emulate iocsr[0x420] as a default value, and it does not support to write. We will add 'TOOD' logs and continue to modify them when using other routing methods later.
You are not considering CSR[0x420][49], which changes the format of this mapping.Thanks very much, I will consider the mapping format by read iocsr[0x420][49] like this:
static uint64_t map_format(void)
{
LoongArchCPU *cpu;
CPULoongArchState *env;
uint64_t val;
cpu = LOONGARCH_CPU(current_cpu);
env = &(cpu->env);
val = address_space_ldq(&env->address_space_iocsr, 0x420,
MEMTXATTRS_UNSPECIFIED, NULL);
val &= 1 << 49;
return val;
}
I'm not 100% sure how this "Other configuration control register" should be handled, but definitely not like this.
[Prev in Thread] | Current Thread | [Next in Thread] |