[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v5 00/22] xen/arm64: Add support for 64KB page in Linux
On Fri, Oct 02, 2015 at 10:51:34AM +0100, Ian Campbell wrote: > (trimming and reordering To/Cc) > > On Thu, 2015-10-01 at 16:15 +0100, David Vrabel wrote: > > On 30/09/15 11:45, Julien Grall wrote: > > > Hi all, > > > > > > ARM64 Linux is supporting both 4KB and 64KB page granularity. Although, > > > Xen > > > hypercall interface and PV protocol are always based on 4KB page > > > granularity. > > > > > > Any attempt to boot a Linux guest with 64KB pages enabled will result > > > to a > > > guest crash. > > > > > > This series is a first attempt to allow those Linux running with the > > > current > > > hypercall interface and PV protocol. > > > > > > This solution has been chosen because we want to run Linux 64KB in > > > released > > > Xen ARM version or/and platform using an old version of Linux DOM0. > > > > Applied to for-linus-4.4, thanks. > > > > Boris, can you kick off a set of tests for this branch, please? > > @Boris, > > Would it be possible to have the results of this test framework posted to > the list, like osstest does? It spews emails per machine per night. There are around 10 of them and they each look like this: FAILED: TEST:tst002(XEN-x86_64) TEST:tst002(XEN-i386): ---------------------------------------------- tst002 (XEN-x86_64): 4.3.0-rc3upstream-00032-g955b2c4 ON Testing tst002 (XEN-x86_64) Test tst002 FAILED: host : tst002.dumpdata.com release : 4.3.0-rc3upstream-00032-g955b2c4 xen_major : 4 xen_minor : 5 xen_changeset : Tue Jul 7 16:09:13 2015 +0100 git:bbbd29a-dirty xen_commandline : compci=115200,8n1 console=compci,vga guest_loglvl=all tmem tmem_compress tmem_dedup dom0_mem=999M,max:1232M +dom0_max_vcpus=2 cpufreq=xen:performance,verbose loglvl=all apic=debug Linux cmdline : earlyprintk=xen debug nofb console=tty console=hvc0 xen-pciback.hide=(07:00.0)(08:05.0)(08:07.0)(08:07.2) +pci=resource_alignment=08:05.0 loglevel=10 Testing.. tst002 (XEN-i386): 4.3.0-rc3upstream-00032-g955b2c4 ON Testing tst002 (XEN-i386) Test tst002 FAILED: host : tst002.dumpdata.com release : 4.3.0-rc3upstream-00032-g955b2c4 xen_major : 4 xen_minor : 5 xen_changeset : Tue Jul 7 16:09:13 2015 +0100 git:bbbd29a-dirty xen_commandline : compci=115200,8n1 console=compci,vga guest_loglvl=all tmem tmem_compress tmem_dedup dom0_mem=999M,max:1232M +dom0_max_vcpus=2 cpufreq=xen:performance,verbose loglvl=all apic=debug Linux cmdline : earlyprintk=xen debug nofb console=tty console=hvc0 xen-pciback.hide=(07:00.0)(08:05.0)(08:07.0)(08:07.2) +pci=resource_alignment=08:05.0 loglevel=10 Testing.. tst002 (BAREMETAL-x86_64): 4.3.0-rc3upstream-00032-g955b2c4 ON tst002 (BAREMETAL-i386): 4.3.0-rc3upstream-00032-g955b2c4 ON And then there is a serial log attached to the email to actually narrow down. Which looks to be (on another machine) (attached the full log) [ 27.822081] switch: port 1(eth0) entered forwarding state Oct 2 09:56:35 tst005 sshd[3475]: WARNING: /etc/ssh/moduli does not exist, using fixed modulus Oct 2 09:56:35 tst005 sshd[3475]: Accepted publickey for root from 192.168.103.1 port 46929 ssh2 Oct 2 09:56:35 tst005 sshd[3475]: Received disconnect from 192.168.103.1: 11: disconnected by user Oct 2 09:56:35 tst005 sshd[3478]: WARNING: /etc/ssh/moduli does not exist, using fixed modulus Oct 2 09:56:35 tst005 sshd[3478]: Accepted publickey for root from 192.168.103.1 port 46930 ssh2 Oct 2 09:56:35 tst005 sshd 192.168.103.1: 11: disconnected by user Oct 2 09:56:35 tst005 sshd[3481]: WARNING: /etc/ssh/moduli does not exist, using fixed modulus Oct 2 09:56:35 tst005 sshd[3481]: Accepted publickey for root from 192.168.103.1 port 46931 ssh2 Oct 2 09:56:35 tst005 init: reloading /etc/inittab (XEN) mm.c:2004:d0v1 Error pfn 0: rd=ffff8302048c7000, od=ffff830204969000, caf=8000000000000001, taf=7400000000000001 (XEN) memory.c:250:d0v1 Bad page free for domain 0 [ 39.926375] ------------[ cut here ]------------ [ 39.927399] kernel BUG at /home/build/linux-boris/drivers/xen/balloon.c:540! [ 39.928361] invalid opcode: 0000 [#1] SMP [ 39.929309] Modules linked in: dm_multipath dm_mod xen_evtchn iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi libcrc32c crc32c_generic sg sd_mod e1000e atl1c tpm_infineon tpm_tis radeon ahci libahci libata scsi_mod ttm backlight wmi xen_blkfront xen_netfront xenfs xen_privcmd [ 39.932391] CPU: 1 PID: 297 Comm: kworker/1:1 Not tainted 4.3.0-rc3upstream-00032-g955b2c4 #1 [ 39.933420] Hardware name: System manufacturer System Product Name/F1A75-M, BIOS 0406 06/11/2011 [ 39.934467] Workqueue: events balloon_process [ 39.935512] task: ffff880037df4ec0 ti: ffff880037078000 task.ti: ffff880037078000 [ 39.936568] RIP: e030:[<ffffffff8142b29b>] [<ffffffff8142b29b>] decrease_reservation+0x32b/0x330 [ 39.937634] RSP: e02b:ffff88003707bca8 EFLAGS: 00010206 [ 39.938696] RAX: 0000000000000000 RBX: dead000000000100 RCX: 0000000000000018 [ 39.939775] RDX: 0000000000000200 RSI: ffff88003707bcc8 RDI: 0000000000000001 [ 39.940849] RBP: ffff88003707bd28 R08: 0000000000000000 R09: 0000000000000001 [ 39.941916] R10: 0000000000007ff0 R11: ffff880038000118 R12: ffffea00009809c0 [ 39.942981] R13: ffff88003707bcc8 R14: 0000000000000200 R15: ffff88003707bce8 [ 39.944050] FS: 00007f9876910740(0000) GS:ffff88003de80000(0000) knlGS:0000000000000000 [ 39.945124] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 39.946189] CR2: 00007f98762d6020 CR3: 0000000001c0f000 CR4: 0000000000000660 [ 39.947259] Stack: [ 39.948302] ffff88003de95880 ffffea00008e68e0 0000000037c5d040 0000000000000200 [ 39.949376] ffffffff81fe7fc0 0000000000000200 0000000000000000 0000000000007ff0 [ 39.950443] ffff88003707bce8 ffff88003707bce8 ffff88003de95080 ffff880037f61400 [ 39.951528] Call Trace: [ 39.952606] [<ffffffff8142b5cc>] balloon_process+0x29c/0x3d0 [ 39.953688] [<ffffffff810d12b0>] ? finish_task_switch+0x70/0x1b0 [ 39.954766] [<ffffffff810ed041>] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [ 39.955848] [<ffffffff810c45e2>] process_one_work+0x142/0x470 [ 39.956915] [<ffffffff810c4a28>] worker_thread+0x118/0x550 [ 39.957972] [<ffffffff810ed041>] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [ 39.959037] [<ffffffff810c4910>] ? process_one_work+0x470/0x470 [ 39.960095] [<ffffffff810c4910>] ? process_one_work+0x470/0x470 [ 39.961129] [<ffffffff810c94f2>] kthread+0xd2/0xf0 [ 39.962152] [<ffffffff810d41c0>] ? schedule_tail+0x20/0xd0 [ 39.963180] [<ffffffff810c9420>] ? kthread_freezable_should_stop+0x80/0x80 [ 39.964219] [<ffffffff8174659f>] ret_from_fork+0x3f/0x70 [ 39.965241] [<ffffffff810c9420>] ? kthread_freezable_should_stop+0x80/0x80 [ 39.966261] Code: be 0f 00 00 00 48 c7 c7 30 c3 95 81 e8 4f 00 c8 ff 48 8b 45 88 e9 cf fd ff ff e8 91 ed c1 ff 0f b6 15 ec 35 8c 00 e9 55 ff ff ff <0f> 0b eb fe 90 55 48 89 e5 41 55 49 89 f5 41 54 53 89 fb 48 c7 [ 39.968536] RIP [<ffffffff8142b29b>] decrease_reservation+0x32b/0x330 [ 39.969626] RSP <ffff88003707bca8> [ 39.970730] ---[ end trace c4a90132ea4ccd65 ]--- [ 39.971882] Kernel panic - not syncing: Fatal exception [ 39.972992] Kernel Offset: disabled Ian, I wrote this long time ago because: - I want the serial logs in the email so I can look at them from my email client. - They were simple smoke tests and didn't need huge infrastructure. - And the reporting is not as snazy as OSSTest. Attachment:
tst005.XEN.txt _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |