From: Claudio Fontana <claudio.fontana@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Chao Peng <chao.p.peng@linux.intel.com>
Cc: Haozhong Zhang <haozhong.zhang@intel.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, anthony.xu@intel.com,
gor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite
Date: Mon, 27 Jun 2016 10:55:02 +0800 [thread overview]
Message-ID: <57709586.1010004@huawei.com> (raw)
In-Reply-To: <92efd563-e5aa-ed71-d3ec-2a11ca2fc982@redhat.com>
Hi Paolo,
On 24.06.2016 14:53, Paolo Bonzini wrote:
>
>
> On 24/06/2016 08:41, Claudio Fontana wrote:
>>> I use qboot for similar goals, you mention that PAM is necessary because of how qboot probes parallel flash,
>>> however in my custom platform I removed PAM completely from QEMU, and everything seems to work without any problems..
>>
>> Btw before you ask: yes I am booting with pflash.
>
> By default low memory points to PCI address space
>
> 00000000000f0000-00000000000fffff (prio 1, RW): alias pam-ram @pc.ram 00000000000f0000-00000000000fffff [disabled]
> 00000000000f0000-00000000000fffff (prio 1, RW): alias pam-pci @pc.ram 00000000000f0000-00000000000fffff [disabled]
> 00000000000f0000-00000000000fffff (prio 1, R-): alias pam-rom @pc.ram 00000000000f0000-00000000000fffff [disabled]
> 00000000000f0000-00000000000fffff (prio 1, RW): alias pam-pci @pci 00000000000f0000-00000000000fffff
>
> All that qboot does is enabling pam-ram:
>
> // Make ram from 0xc0000-0xf0000 read-write
> int i;
> for (i=0; i<6; i++) {
> int pam = pambase + 1 + i;
> pci_config_writeb(bdf, pam, 0x33);
> }
>
> // Make ram from 0xf0000-0x100000 read-write and shadow BIOS
> // We're still running from 0xffff0000
> pci_config_writeb(bdf, pambase, 0x30);
> memcpy(low_start, bios_start, 0x10000);
>
> So if you remove PAM but you are leaving 0xC000-0x10000 pointing to
> RAM, you are effectively moving qboot's PAM configuration to QEMU. :)
>
> Of these writes, only the last write is strictly necessary. qboot
> currently uses 0xe0000-0xf0000 for the ACPI tables but we could move
> them to the EBDA instead and save the initial loop. But I'd like to
> see a trace saying how much time is spent configuring PAM exactly.
>
> Paolo
>
In my case the boot times are satisfactory including the PAM configuration loop in qboot.
The reason I removed the PAM backend in QEMU (or rather, made them configurable via existing CONFIG_PAM),
is as part of memory saving patches, not because of boottime issues.
Ciao,
Claudio
next prev parent reply other threads:[~2016-06-27 2:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 8:14 [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 1/9] acpi: introduce light weight ACPI PM emulation pm-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 2/9] pci: introduce light weight PCIE Host emulation pci-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 3/9] acpi: add support for pc-lite platform Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 4/9] acpi: expose data structurs and functions of BIOS linker loader Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 5/9] acpi: expose acpi_checksum() Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 6/9] acpi: patch guest ACPI for pc-lite Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 7/9] pc: skip setting CMOS data when RTC device is unavailable Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 8/9] pc: support direct loading protected/long mode kernel Chao Peng
2016-06-17 8:14 ` [Qemu-devel] [RFC 9/9] pc: introduce light weight PC board pc-lite Chao Peng
2016-06-17 13:24 ` [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite Paolo Bonzini
2016-06-20 6:01 ` Chao Peng
2016-06-20 6:54 ` Paolo Bonzini
2016-06-20 12:31 ` Stefan Hajnoczi
2016-06-20 13:00 ` Paolo Bonzini
2016-06-21 1:23 ` Chao Peng
2016-06-21 16:44 ` Michael S. Tsirkin
2016-06-23 8:32 ` Chao Peng
2016-06-23 12:44 ` Paolo Bonzini
2016-06-24 6:39 ` Claudio Fontana
2016-06-24 6:41 ` Claudio Fontana
2016-06-24 6:53 ` Paolo Bonzini
2016-06-27 2:55 ` Claudio Fontana [this message]
2016-06-28 9:27 ` Chao Peng
2016-06-20 10:36 ` Dr. David Alan Gilbert
2016-06-19 3:51 ` Michael S. Tsirkin
2016-06-20 6:12 ` Chao Peng
2016-06-23 12:55 ` Daniel P. Berrange
2016-06-28 10:10 ` Chao Peng
2016-06-28 10:26 ` Daniel P. Berrange
2016-06-19 8:21 ` Claudio Fontana
2016-06-20 6:30 ` Chao Peng
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=57709586.1010004@huawei.com \
--to=claudio.fontana@huawei.com \
--cc=anthony.xu@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=haozhong.zhang@intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.