From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Su Hang <suhang16@mails.ucas.ac.cn>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
jim@groklearning.com, mail@steffen-goertz.de, ilg@livius.net,
Alistair Francis <alistair@alistair23.me>,
Subbaraya Sundeep <sundeep.lkml@gmail.com>,
Steffen Gortz <qemu.ml@steffen-goertz.de>,
qemu-arm@nongnu.org, Joel Stanley <joel@jms.id.au>,
jusual@mail.ru
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH v4 5/6] loader: Implement .hex file loader
Date: Mon, 13 Aug 2018 16:56:22 +0100 [thread overview]
Message-ID: <20180813155622.GA18429@stefanha-x1.localdomain> (raw)
In-Reply-To: <1a84a9fc-93f8-3573-c27e-bb60d9c48a7a@amsat.org>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
On Fri, Aug 10, 2018 at 02:00:44AM -0300, Philippe Mathieu-Daudé wrote:
> On 08/03/2018 11:47 AM, Stefan Hajnoczi wrote:
> > + parser->rom_start_address = parser->next_address_to_write;
> > + parser->current_rom_index = 0;
> > + break;
> > +
> > + case START_SEG_ADDR_RECORD:
> > + if (line->byte_count != 4 && line->address != 0) {
> > + return -1;
> > + }
> > +
> > + /* x86 16-bit CS:IP segmented addressing */
> > + *(parser->start_addr) = (((line->data[0] << 8) | line->data[1]) << 4) |
> > + (line->data[2] << 8) | line->data[3];
>
> Can you add a qtest for this case?
> For the HEX loader I understand the specs as this is the same parsing as
> the START_LINEAR_ADDR_RECORD case; so I disagree with data[0] and
> data[1] shifts.
x86 real-mode CS:IP addressing means (CS << 4) + IP. It produces 24-bit
addresses on 80286 and later. This is not the same as
START_LINEAR_ADDR_RECORD.
GNU bfd implements it as follows:
abfd->start_address += (HEX4 (buf) << 4) + HEX4 (buf + 4);
https://sourceware.org/git/?p=binutils.git;a=blob;f=bfd/ihex.c;h=09f756a1c2c11e57c5da15a6ff96491275575b86;hb=HEAD#l415
Thanks for commenting on this, I had written (CS << 4) | IP instead of
(CS << 4) + IP. This will be fixed in the next revision.
> This is different for the consumer (i386 expects 2 16-bit registers but
> HexParser->start_addr is a hwaddr, used as a single (at least) 32-bit
> register.
I think you're saying that on x86 the guest CS:IP registers should be
set. This loader is never called from hw/i386/ so it doesn't matter at
this time.
GNU bfd uses START_SEG_ADDR_RECORD records on non-x86 architectures
where there are no segment registers and that's where we've encountered
them.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-08-13 15:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 14:47 [Qemu-devel] [PATCH v4 0/6] arm: add Cortex M0 CPU model and hex file loader Stefan Hajnoczi
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 1/6] hw/arm: make bitbanded IO optional on ARMv7-M Stefan Hajnoczi
2018-08-10 3:31 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 2/6] target/arm: add "cortex-m0" CPU model Stefan Hajnoczi
2018-08-10 3:38 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 3/6] loader: extract rom_free() function Stefan Hajnoczi
2018-08-08 21:32 ` Alistair Francis
2018-08-10 3:39 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 4/6] loader: add rom transaction API Stefan Hajnoczi
2018-08-08 21:31 ` Alistair Francis
2018-08-13 9:58 ` Stefan Hajnoczi
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 5/6] loader: Implement .hex file loader Stefan Hajnoczi
2018-08-10 5:00 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-08-10 10:25 ` sail darcy
2018-08-13 15:56 ` Stefan Hajnoczi [this message]
2018-08-15 14:18 ` Philippe Mathieu-Daudé
2018-08-15 17:52 ` Stefan Hajnoczi
2018-08-16 16:10 ` Philippe Mathieu-Daudé
2018-08-03 14:47 ` [Qemu-devel] [PATCH v4 6/6] Add QTest testcase for the Intel Hexadecimal Stefan Hajnoczi
2018-08-10 4:26 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-08-13 18:49 ` Stefan Hajnoczi
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=20180813155622.GA18429@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alistair@alistair23.me \
--cc=f4bug@amsat.org \
--cc=ilg@livius.net \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jusual@mail.ru \
--cc=mail@steffen-goertz.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu.ml@steffen-goertz.de \
--cc=suhang16@mails.ucas.ac.cn \
--cc=sundeep.lkml@gmail.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).