From: Paolo Bonzini <pbonzini@redhat.com>
To: "Montes, Julio" <julio.montes@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "mst@redhat.com" <mst@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/i386: Fix linker error when ISAPC is disabled
Date: Wed, 3 Jul 2019 23:09:30 +0200 [thread overview]
Message-ID: <be6aa304-a8e4-d64a-432f-24d52e42c097@redhat.com> (raw)
In-Reply-To: <69cb55e2b337cd24f195305683a070cda8b0befd.camel@intel.com>
On 03/07/19 18:40, Montes, Julio wrote:
> On Wed, 2019-07-03 at 18:21 +0200, Paolo Bonzini wrote:
>> On 03/07/19 17:49, Julio Montes wrote:
>>> In pc_init1(), ISA IDE is initialized without checking if ISAPC or
>>> IDE_ISA
>>> configs are enabled. This results in a link error when
>>> CONFIG_ISAPC is set to 'n' in the file default-configs/i386-
>>> softmmu.mak:
>>>
>>> hw/i386/pc_piix.o: In function `pc_init1':
>>> hw/i386/pc_piix.c:261: undefined reference to `isa_ide_init'
>>> hw/i386/pc_piix.c:261: undefined reference to `isa_ide_init'
>>>
>>> Place ide_isa code under #ifdef CONFIG_IDE_ISA to fix linker errors
>>
>> But there is nothing that defines CONFIG_IDE_ISA, right?
>
> yes I think you're right, do I need to use #ifdef CONFIG_ISAPC instead?
> or how I can define CONFIG_IDE_ISA at build time?
No, Kconfig symbols do not end up in any header. We could have one that
is only included in obj-y files though, since hw/i386/pc_piix.c is obj-y
rather than common-obj-y.
Paolo
>>
>> Paolo
>>
>>> Signed-off-by: Julio Montes <julio.montes@intel.com>
>>> ---
>>> hw/i386/pc_piix.c | 11 ++++++++---
>>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
>>> index c07c4a5b38..b93f9327be 100644
>>> --- a/hw/i386/pc_piix.c
>>> +++ b/hw/i386/pc_piix.c
>>> @@ -61,9 +61,11 @@
>>>
>>> #define MAX_IDE_BUS 2
>>>
>>> +#ifdef CONFIG_IDE_ISA
>>> static const int ide_iobase[MAX_IDE_BUS] = { 0x1f0, 0x170 };
>>> static const int ide_iobase2[MAX_IDE_BUS] = { 0x3f6, 0x376 };
>>> static const int ide_irq[MAX_IDE_BUS] = { 14, 15 };
>>> +#endif
>>>
>>> /* PC hardware initialisation */
>>> static void pc_init1(MachineState *machine,
>>> @@ -254,7 +256,10 @@ static void pc_init1(MachineState *machine,
>>> }
>>> idebus[0] = qdev_get_child_bus(&dev->qdev, "ide.0");
>>> idebus[1] = qdev_get_child_bus(&dev->qdev, "ide.1");
>>> - } else {
>>> + pc_cmos_init(pcms, idebus[0], idebus[1], rtc_state);
>>> + }
>>> +#ifdef CONFIG_IDE_ISA
>>> +else {
>>> for(i = 0; i < MAX_IDE_BUS; i++) {
>>> ISADevice *dev;
>>> char busname[] = "ide.0";
>>> @@ -268,9 +273,9 @@ static void pc_init1(MachineState *machine,
>>> busname[4] = '0' + i;
>>> idebus[i] = qdev_get_child_bus(DEVICE(dev), busname);
>>> }
>>> + pc_cmos_init(pcms, idebus[0], idebus[1], rtc_state);
>>> }
>>> -
>>> - pc_cmos_init(pcms, idebus[0], idebus[1], rtc_state);
>>> +#endif
>>>
>>> if (pcmc->pci_enabled && machine_usb(machine)) {
>>> pci_create_simple(pci_bus, piix3_devfn + 2, "piix3-usb-
>>> uhci");
>>>
next prev parent reply other threads:[~2019-07-03 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 15:49 [Qemu-devel] [PATCH] hw/i386: Fix linker error when ISAPC is disabled Julio Montes
2019-07-03 16:21 ` Paolo Bonzini
2019-07-03 16:40 ` Montes, Julio
2019-07-03 21:09 ` Paolo Bonzini [this message]
2019-07-04 18:03 ` Julio Montes
2019-07-04 19:36 ` no-reply
2019-07-05 8:25 ` Paolo Bonzini
2019-07-05 8:25 ` Paolo Bonzini
2019-07-05 17:20 ` no-reply
2019-07-05 17:25 ` Philippe Mathieu-Daudé
2019-07-05 19:23 ` Montes, Julio
2019-07-03 20:09 ` no-reply
2019-07-05 14:35 ` [Qemu-devel] [PATCH v2 1/2] Makefile: generate header file with the list of devices enabled Julio Montes
2019-07-05 14:35 ` [Qemu-devel] [PATCH v2 2/2] hw/i386: Fix linker error when ISAPC is disabled Julio Montes
2019-07-05 16:34 ` Paolo Bonzini
2019-07-05 19:40 ` Philippe Mathieu-Daudé
2019-07-06 4:21 ` [Qemu-devel] [PATCH v2 1/2] Makefile: generate header file with the list of devices enabled Markus Armbruster
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=be6aa304-a8e4-d64a-432f-24d52e42c097@redhat.com \
--to=pbonzini@redhat.com \
--cc=julio.montes@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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).