public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Kautuk Consul <kconsul@ventanamicro.com>
Cc: Sean Anderson <sean.anderson@seco.com>,
	Bin Meng <bmeng.cn@gmail.com>,
	Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
	Rick Chen <rick@andestech.com>, Simon Glass <sjg@chromium.org>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Alexandru Gagniuc <mr.nuke.me@gmail.com>,
	Philippe Reynes <philippe.reynes@softathome.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	"Eugen Hristev" <eugen.hristev@microchip.com>,
	Stefan Roese <sr@denx.de>,
	"Loic Poulain" <loic.poulain@linaro.org>,
	Peng Fan <peng.fan@nxp.com>, Michal Simek <michal.simek@amd.com>,
	<u-boot@lists.denx.de>, <ycliang@andestech.com>
Subject: Re: [PATCH v5 3/3] board: qemu-riscv: enable semihosting
Date: Wed, 7 Dec 2022 07:01:09 +0000	[thread overview]
Message-ID: <Y5A6Nb2Fsl1EDWhE@ubuntu01> (raw)
In-Reply-To: <CALwhnKDokA10ySFxLLMcuOK-qgWzT+r8gaeg9XPK2NVGbjP3ZQ@mail.gmail.com>

Hi Kautuk,

On Tue, Dec 06, 2022 at 05:02:49PM +0530, Kautuk Consul wrote:
> Hi Leo,
> 
> On Tue, Dec 6, 2022 at 4:29 PM Leo Liang <ycliang@andestech.com> wrote:
> >
> > Hi Kautuk,
> >
> > We have tested your patchset with QEMU 7.1.0.
> > It generally looks fine, but CI error seems to persist.
> > https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/14314
> >
> > The error comes from CI testcase timed-out.
> > The reason for the time-out is not yet confirmed,
> > but we suspect it's because when executing under semihosting,
> > QEMU could not exit normally. (thru ctrl+x a)
> >
> > There is a seemingly relevent patchset that sits on QEMU mailing list for some time.
> > https://lore.kernel.org/all/20220620190834.GA16887@ws2101.lin.mbt.kalray.eu/T/#m1bc32cc32511b6ac8adfaf67983dc2bccd4b9ec9
> >
> > On the u-boot side, what do you think if we disable semihosting by default?
> > (i.e., not adding CONFIG_SEMIHOSTING_XXX in qemu's defconfig)
> 
> I think it is okay to disable semihosting by default. Then the user
> will configure it when needed.
> So then can you ACK the first 2 patches ? I think we can leave out the
> 3rd qemu config patch for now.
>

No problem!
Additionally, could you rebase the patchset to current master, 
add what Sean suggested, and then send again?
I think I could merge your patch as soon as you re-send it.

Best regards,
Leo

> >
> > Best regards,
> > Leo
> >
> > On Tue, Dec 06, 2022 at 11:12:41AM +0530, Kautuk Consul wrote:
> > > Hi,
> > >
> > > On Mon, Dec 5, 2022 at 8:46 PM Sean Anderson <sean.anderson@seco.com> wrote:
> > > >
> > > > On 12/5/22 00:51, Kautuk Consul wrote:
> > > > > Hi,
> > > > >
> > > > > On Sat, Dec 3, 2022 at 9:44 AM Bin Meng <bmeng.cn@gmail.com> wrote:
> > > > >>
> > > > >> On Fri, Sep 23, 2022 at 3:03 PM Kautuk Consul <kconsul@ventanamicro.com> wrote:
> > > > >> >
> > > > >> > To enable semihosting we also need to enable the following
> > > > >> > configs in defconfigs:
> > > > >> > CONFIG_SEMIHOSTING
> > > > >> > CONFIG_SPL_SEMIHOSTING
> > > > >> > CONFIG_SEMIHOSTING_SERIAL
> > > > >> > CONFIG_SERIAL_PROBE_ALL
> > > > >> > CONFIG_SPL_FS_EXT4
> > > > >> > CONFIG_SPL_FS_FAT
> > > > >>
> > > > >> Why should these _SPL_FS_xxx be required? If it's required by
> > > > >> SEMIHOSTING, could the dependency be fixed there?
> > > > >
> > > > > The build dependencies require that these options be there.
> > > >
> > > > What error do you get?
> > >
> > > If I disable both the _SPL_FS_* config options then I get the
> > > following compilation error:
> > > common/spl/spl_semihosting.c: In function 'spl_smh_load_image':
> > > common/spl/spl_semihosting.c:27:32: error:
> > > 'CONFIG_SPL_FS_LOAD_PAYLOAD_NAME' undeclared (first use in this
> > > function)
> > >    27 |         const char *filename = CONFIG_SPL_FS_LOAD_PAYLOAD_NAME;
> > >       |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > common/spl/spl_semihosting.c:27:32: note: each undeclared identifier
> > > is reported only once for each function it appears in
> > >
> > > Bin/Sean: This error is not really related to the semihosting feature
> > > but is related to COFIG_SPL in general.
> > > Can you please accept this patch-set and then I'll try and find time
> > > in the future maybe to rectify this build dependency
> > > problem ?
> > >
> > > >
> > > > --Sean
> > > >
> > > > >>
> > > > >> >
> > > > >> > Signed-off-by: Kautuk Consul <kconsul@ventanamicro.com>
> > > > >> > ---
> > > > >> >  configs/qemu-riscv32_defconfig       | 4 ++++
> > > > >> >  configs/qemu-riscv32_smode_defconfig | 4 ++++
> > > > >> >  configs/qemu-riscv32_spl_defconfig   | 7 +++++++
> > > > >> >  configs/qemu-riscv64_defconfig       | 4 ++++
> > > > >> >  configs/qemu-riscv64_smode_defconfig | 4 ++++
> > > > >> >  configs/qemu-riscv64_spl_defconfig   | 7 +++++++
> > > > >> >  6 files changed, 30 insertions(+)
> > > > >> >
> > > > >>
> > > > >> Regards,
> > > > >> Bin
> > > >

  reply	other threads:[~2022-12-07  7:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  7:03 [PATCH v5 0/3] Add riscv semihosting support in u-boot Kautuk Consul
2022-09-23  7:03 ` [PATCH v5 1/3] lib: Add common semihosting library Kautuk Consul
2022-10-10 15:39   ` Sean Anderson
2022-09-23  7:03 ` [PATCH v5 2/3] arch/riscv: add semihosting support for RISC-V Kautuk Consul
2022-10-10 15:43   ` Sean Anderson
     [not found]   ` <HK0PR03MB2994013C655E85AF1F3D2CFBC1229@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-10-12  1:40     ` Rick Chen
2022-09-23  7:03 ` [PATCH v5 3/3] board: qemu-riscv: enable semihosting Kautuk Consul
2022-10-05  6:17   ` Leo Liang
2022-10-06  5:13     ` Kautuk Consul
     [not found]   ` <HK0PR03MB29949257906C387D549119EBC1229@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-10-12  1:33     ` Rick Chen
2022-12-03  4:14   ` Bin Meng
2022-12-05  5:51     ` Kautuk Consul
2022-12-05 13:54       ` Bin Meng
2022-12-05 15:16       ` Sean Anderson
2022-12-06  5:42         ` Kautuk Consul
2022-12-06 10:58           ` Leo Liang
2022-12-06 11:32             ` Kautuk Consul
2022-12-07  7:01               ` Leo Liang [this message]
2022-12-07 11:47                 ` Kautuk Consul
2022-12-06 15:16           ` Sean Anderson
2022-11-29  6:29 ` [PATCH v5 0/3] Add riscv semihosting support in u-boot Kautuk Consul
2022-11-29  6:36   ` Bin Meng
2022-11-29  6:57     ` Kautuk Consul
2022-12-02  8:46       ` Leo Liang
2022-12-02  9:52         ` Kautuk Consul
2022-12-02 12:01           ` Leo Liang
2022-12-03  4:28       ` Bin Meng
2022-12-03  6:01         ` Bin Meng
2022-12-05  5:50           ` Kautuk Consul

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=Y5A6Nb2Fsl1EDWhE@ubuntu01 \
    --to=ycliang@andestech.com \
    --cc=bmeng.cn@gmail.com \
    --cc=eugen.hristev@microchip.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kconsul@ventanamicro.com \
    --cc=loic.poulain@linaro.org \
    --cc=michal.simek@amd.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=philippe.reynes@softathome.com \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=rayagonda.kokatanur@broadcom.com \
    --cc=rick@andestech.com \
    --cc=sean.anderson@seco.com \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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