From: Vitaly Wool <vitaly.wool@konsulko.com>
To: Alex Ghiti <alex@ghiti.fr>
Cc: Palmer Dabbelt <palmerdabbelt@google.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Bin Meng <bin.meng@windriver.com>,
Anup Patel <anup@brainfault.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [PATCH v6] RISC-V: enable XIP
Date: Wed, 7 Apr 2021 10:38:05 +0200 [thread overview]
Message-ID: <CAM4kBBLsWPVfL20Py=QVSUCT4QW6pDbJR_TVR=LtTVgMLqL1QQ@mail.gmail.com> (raw)
In-Reply-To: <dd303c4c-713f-c68c-879d-f4212cc305ee@ghiti.fr>
Hi Alex,
<snip>
> > All in all, I am quite sure now that your take on XIP is working fine.
> > The issue with single-core boot under QEmu seems to be less
> > reproducible on slower machines running QEmu and more reproducible on
> > higher performance ones. It's not clear to me if that is a QEmu
> > problem or an in-kernel race, but it's hardly a XIP problem: I was
> > able to reproduce it once on a non-XIP kernel too, by copying it to
> > RAM in u-boot and giving it a 'go'.
>
> Ok then I'll post a v7 of your patch soon hoping it will go to for-next.
> I'll add my SoB to yours as I modified quite a few things and I thin
> people need to know who to yell at, if you don't mind of course.
No, absolutely not. :) Thanks for digging into this!
Best regards,
Vitaly
next prev parent reply other threads:[~2021-04-07 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 0:12 [PATCH v6] RISC-V: enable XIP Vitaly Wool
2021-03-30 6:23 ` Palmer Dabbelt
2021-03-30 6:26 ` Vitaly Wool
2021-03-30 18:39 ` Alex Ghiti
2021-03-30 19:33 ` Palmer Dabbelt
2021-03-30 20:04 ` Alex Ghiti
2021-04-01 8:11 ` Alex Ghiti
2021-04-01 8:52 ` Vitaly Wool
2021-04-01 11:10 ` Alex Ghiti
2021-04-03 9:59 ` Alex Ghiti
2021-04-04 8:39 ` Vitaly Wool
2021-04-05 8:34 ` Vitaly Wool
2021-04-06 6:47 ` Alex Ghiti
2021-04-06 7:54 ` Vitaly Wool
2021-04-06 18:28 ` Alex Ghiti
2021-04-07 8:38 ` Vitaly Wool [this message]
2021-03-31 8:37 ` Kefeng Wang
2021-03-31 12:59 ` Vitaly Wool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM4kBBLsWPVfL20Py=QVSUCT4QW6pDbJR_TVR=LtTVgMLqL1QQ@mail.gmail.com' \
--to=vitaly.wool@konsulko.com \
--cc=Alistair.Francis@wdc.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=bin.meng@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nico@fluxnic.net \
--cc=palmerdabbelt@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).