From: Christopher Friedt
In the case that size1 was zero, because of the explicit
'end1 > addr' check, the range check would fail and the error
message would read as shown below. The correct comparison
is 'end1 >= addr' (or 'addr <= end1').
EDU: DMA range 0x4-0x3 out of bounds (0x4-0
On 10/14/22 11:40, Qi Hu wrote:
Similar to the ARM64, LoongArch has PC-relative instructions such as
PCADDU18I. These instructions can be used to support direct jump for
LoongArch. Additionally, if instruction "B offset" can cover the target
address(target is within ±128MB range), a single "B off
Hi Jason,
On Thu, Oct 13, 2022 at 08:16:51PM -0600, Jason A. Donenfeld wrote:
> When the system reboots, the rng-seed that the FDT has should be
> re-randomized, so that the new boot gets a new seed. Since the FDT is in
> the ROM region at this point, we add a hook right after the ROM has been
> a
On 10/15/22 17:27, Qi Hu wrote:
Similar to the ARM64, LoongArch has PC-relative instructions such as
PCADDU18I. These instructions can be used to support direct jump for
LoongArch. Additionally, if instruction "B offset" can cover the target
address(target is within ±128MB range), a single "B off
On 10/15/22 10:20, BALATON Zoltan wrote:
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/15/22 08:40, BALATON Zoltan wrote:
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/14/22 19:52, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Daniel Henrique Barboza wrote:
Zoltan,
G
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/15/22 08:40, BALATON Zoltan wrote:
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/14/22 19:52, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Daniel Henrique Barboza wrote:
Zoltan,
Gitlab didn't like this patch. It broke all 32
On Freitag, 14. Oktober 2022 00:00:58 CEST Paolo Bonzini wrote:
[...]
> However, it seems like a lost battle. :( Some of the optimizations are
> stuff that you should just not have to do, for example only invoking
> "x.kind" once (because it's a property not a field). Another issue is
> that the bi
Thank you very much for the review!
I have a few questions:
On 27.09.22 15:50, Peter Maydell wrote:
On Sat, 20 Aug 2022 at 15:19, wrote:
From: Tobias Röhmel
Signed-off-by: Tobias Röhmel
---
target/arm/cpu.h| 10 +++
target/arm/helper.c | 171
Patches 1, 6 and 8-15 applied to ppc-next.
Thanks,
Daniel
On 9/26/22 14:38, Daniel Henrique Barboza wrote:
Hi,
This new version contains all changes proposed during the review process,
all of them done in the patch that introduces dumpdtb.
Other changes made:
- Patch 14/14, the one that i
On 10/15/22 08:40, BALATON Zoltan wrote:
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/14/22 19:52, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Daniel Henrique Barboza wrote:
Zoltan,
Gitlab didn't like this patch. It broke all 32 bits builds due to an overflow
down there:
On 9/
On Sat, 15 Oct 2022, Daniel Henrique Barboza wrote:
On 10/14/22 19:52, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Daniel Henrique Barboza wrote:
Zoltan,
Gitlab didn't like this patch. It broke all 32 bits builds due to an
overflow
down there:
On 9/24/22 09:28, BALATON Zoltan wrote:
Move th
On 10/14/22 19:52, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Daniel Henrique Barboza wrote:
Zoltan,
Gitlab didn't like this patch. It broke all 32 bits builds due to an overflow
down there:
On 9/24/22 09:28, BALATON Zoltan wrote:
Move the check for valid memory sizes from board to sdram c
Similar to the ARM64, LoongArch has PC-relative instructions such as
PCADDU18I. These instructions can be used to support direct jump for
LoongArch. Additionally, if instruction "B offset" can cover the target
address(target is within ±128MB range), a single "B offset" plus a nop
will be used by "t
13 matches
Mail list logo
