From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Wei Liu" <wl@xen.org>, "Jan Beulich" <JBeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH v2 0/5] x86: Remove more 16M total-size restrictions
Date: Fri, 17 Jan 2020 20:42:18 +0000 [thread overview]
Message-ID: <20200117204223.30076-1-andrew.cooper3@citrix.com> (raw)
The boot/directmap pagetables, high Xen pagetables, and use of BOOT_FS all
come with arbitrary limitations to Xen's total size. Remove these limits.
Testing of the EFI build indicates that there is still an issue lurking
somewhere:
(XEN) ----[ Xen-4.14-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d0802557fa>] drivers/char/ns16550.c#ns16550_poll+0x1d/0x21
...
(XEN) Xen call trace:
(XEN) [<ffff82d0802557fa>] R drivers/char/ns16550.c#ns16550_poll+0x1d/0x21
(XEN) [<ffff82d080247446>] F common/timer.c#execute_timer+0x49/0x64
(XEN) [<ffff82d080247c24>] F common/timer.c#timer_softirq_action+0xa2/0x276
(XEN) [<ffff82d080243b81>] F common/softirq.c#__do_softirq+0x71/0x9a
(XEN) [<ffff82d080243bdd>] F process_pending_softirqs+0x33/0x37
(XEN) [<ffff82d0812bd1be>] F __cpu_up+0x652/0x719
(XEN) [<ffff82d080204874>] F cpu_up+0x75/0xe3
(XEN) [<ffff82d08162ad43>] F __start_xen+0x251a/0x29b1
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL TRAP: vector = 6 (invalid opcode)
(XEN) ****************************************
which is run_in_exception_handler() not being recognised as BUGFRAME_run_fn.
Therefore, I've left the linker assert in place for now.
Andrew Cooper (5):
x86/boot: Create the l2_xenmap[] mappings dynamically
x86/boot: Size the boot/directmap mappings dynamically
x86/boot: Drop explicit %fs uses
x86/boot: Simplify pagetable manipulation loops
x86/boot: Drop sym_fs()
xen/arch/x86/boot/head.S | 145 +++++++++++++++++++++++------------------
xen/arch/x86/boot/trampoline.S | 1 -
xen/arch/x86/boot/x86_64.S | 23 +++----
xen/arch/x86/efi/efi-boot.h | 37 +++++++++--
xen/arch/x86/xen.lds.S | 3 +
5 files changed, 126 insertions(+), 83 deletions(-)
--
2.11.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2020-01-17 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 20:42 Andrew Cooper [this message]
2020-01-17 20:42 ` [Xen-devel] [PATCH v2 1/5] x86/boot: Create the l2_xenmap[] mappings dynamically Andrew Cooper
2020-01-20 10:29 ` Jan Beulich
2020-01-17 20:42 ` [Xen-devel] [PATCH v2 2/5] x86/boot: Size the boot/directmap " Andrew Cooper
2020-01-20 10:30 ` Jan Beulich
2020-01-17 20:42 ` [Xen-devel] [PATCH v2 3/5] x86/boot: Drop explicit %fs uses Andrew Cooper
2020-01-20 10:35 ` Jan Beulich
2020-01-17 20:42 ` [Xen-devel] [PATCH v2 4/5] x86/boot: Simplify pagetable manipulation loops Andrew Cooper
2020-01-20 10:46 ` Jan Beulich
2020-01-22 15:43 ` Andrew Cooper
2020-01-17 20:42 ` [Xen-devel] [PATCH v2 5/5] x86/boot: Drop sym_fs() Andrew Cooper
2020-01-20 11:39 ` Jan Beulich
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=20200117204223.30076-1-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.