Re: [PATCH] target/riscv: fix check of guest pa top bits

2020-05-01 Thread Jonathan Behrens
Yeah, I've run into the same issue. Even if you ask Gmail to treat the email as plain text it still takes the liberty of hard wrapping lines without asking you. It really is a shame that there isn't a good way to submit patches via a web UI, the art of git send-email + manual SMTP isn't as

Re: [PATCH] target/riscv: fix check of guest pa top bits

2020-05-01 Thread Jose Martins
Just resubmitted version 2. Sorry. Not really used to this. I actually wasn't using git send-email. I was copying the patch to my email client which was causing the weird wrapping. I think I also fixed the issues raised by checkpatch. Hope everything is correct now. Jose On Thu, 30 Apr 2020 at

Re: [PATCH] target/riscv: fix check of guest pa top bits

2020-04-30 Thread Alistair Francis
On Thu, Apr 30, 2020 at 12:45 PM Alistair Francis wrote: > > On Fri, Apr 24, 2020 at 8:10 AM Jose Martins wrote: > > > > The spec states that on sv39x4 guest physical "address bits 63:41 > > must all be zeros, or else a guest-page-fault exception occurs.". > > However, the check performed for

Re: [PATCH] target/riscv: fix check of guest pa top bits

2020-04-30 Thread Alistair Francis
On Fri, Apr 24, 2020 at 8:10 AM Jose Martins wrote: > > The spec states that on sv39x4 guest physical "address bits 63:41 > must all be zeros, or else a guest-page-fault exception occurs.". > However, the check performed for these top bits of the virtual address > on the second stage is the same

[PATCH] target/riscv: fix check of guest pa top bits

2020-04-24 Thread Jose Martins
The spec states that on sv39x4 guest physical "address bits 63:41 must all be zeros, or else a guest-page-fault exception occurs.". However, the check performed for these top bits of the virtual address on the second stage is the same as the one performed for virtual addresses on the first stage