Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1303753
| From | Peter Maydell <peter.maydell@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' |
| Date | 2016-01-07 18:30 +0100 |
| Message-ID | <qOmxQ-2P2-21@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <qOiNA-eq-1@gated-at.bofh.it> <qOl8K-1I5-17@gated-at.bofh.it> <qOl8M-1I5-65@gated-at.bofh.it> <qOlLs-2e2-15@gated-at.bofh.it> <qOmoa-2Kl-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 7 January 2016 at 17:10, Guenter Roeck <linux@roeck-us.net> wrote: > Strictly speaking you may be right (regression is a bit strong, though), > but for my part I tend to be pragmatic. > > A warning message such as "Access to unimplemented register X" may be > useful You can get these from QEMU if you pass it "-d unimp", which logs various kinds of things-not-yet-implemented, with a couple of caveats: * the warning is when we translate the code, not when we execute it * it won't warn for registers which we implement but not completely (eg only partial functionality or dummy reads-as-written) In this case it printed "write access to unsupported AArch64 system register op0:3 op1:3 crn:9 crm:14 op2:0" The 'guest_errors' suboption to -d warns about things which appear to be errors in the guest OS, for instance some kinds of UNPREDICTABLE, and may also be of interest. Neither guest_errors nor unimp are comprehensive (there are many more situations where we don't warn than where we do) but they can be helpful sometimes. thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Peter Maydell <peter.maydell@linaro.org> - 2016-01-07 14:30 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2016-01-07 17:00 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Peter Maydell <peter.maydell@linaro.org> - 2016-01-07 17:00 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2016-01-07 17:40 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Peter Maydell <peter.maydell@linaro.org> - 2016-01-07 18:00 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Guenter Roeck <linux@roeck-us.net> - 2016-01-07 18:20 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Guenter Roeck <linux@roeck-us.net> - 2016-01-07 18:20 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Peter Maydell <peter.maydell@linaro.org> - 2016-01-07 18:30 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2016-01-07 19:40 +0100
Re: [Qemu-devel] arm64 qemu tests failing in linux-next since 'arm64: kernel: enforce pmuserenr_el0 initialization and restore' Guenter Roeck <linux@roeck-us.net> - 2016-01-07 17:30 +0100
csiph-web