similar to: [PATCH 2/10] I386 acpi remove earlyquirk warning.patch

On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > Do you have any suggestions for the case where the pcieport driver > refuses to put the bridge in D3 (because the BIOS is too old)? In that > case the nouveau driver needs to fallback to the DSM method (but not > when runtime PM is deliberately disabled by writing control=on). The BIOS cut-off date is meant to avoid issues

Currently when X86 && ACPI && !X86_PLATFORM_DEVICES kbuild spits: warning: (DRM_NOUVEAU) selects ACPI_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI) warning: (DRM_NOUVEAU) selects MXM_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI_WMI) and goes on, which leaves a situation where ACPI_WMI

Currently when X86 && ACPI && !X86_PLATFORM_DEVICES kbuild spits: warning: (DRM_NOUVEAU) selects ACPI_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI) warning: (DRM_NOUVEAU) selects MXM_WMI which has unmet direct dependencies (X86 && X86_PLATFORM_DEVICES && ACPI_WMI) and goes on, which leaves a situation where ACPI_WMI

On Tue, May 31, 2016 at 02:20:26PM +0200, Lukas Wunner wrote: > On Mon, May 30, 2016 at 06:13:51PM +0200, Peter Wu wrote: > > Do you have any suggestions for the case where the pcieport driver > > refuses to put the bridge in D3 (because the BIOS is too old)? In that > > case the nouveau driver needs to fallback to the DSM method (but not > > when runtime PM is

Some notebook computer systems expose the EDID for the internal panel via the ACPI _DDC method. On some systems this is because the panel does not populate the hardware DDC lines, and on some systems with dynamic display muxes, _DDC is implemented to allow the internal panel's EDID to be read at any time, regardless of how the mux is switched. The _DDC method can be implemented for each

Added the match table and pointers for ACPI probing to the driver. This uses the same identifier for virt devices as being used for qemu ARM64 ACPI support. http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e Signed-off-by: Graeme Gregory <graeme.gregory at linaro.org> --- drivers/virtio/virtio_mmio.c | 10 ++++++++++ 1 file changed, 10

Added the match table and pointers for ACPI probing to the driver. This uses the same identifier for virt devices as being used for qemu ARM64 ACPI support. http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e Signed-off-by: Graeme Gregory <graeme.gregory at linaro.org> --- drivers/virtio/virtio_mmio.c | 10 ++++++++++ 1 file changed, 10

On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> Added the match table and pointers for ACPI probing to the driver. >> >> This uses the same identifier for virt devices as being used for qemu >> ARM64 ACPI support. >> >>

On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> Added the match table and pointers for ACPI probing to the driver. >> >> This uses the same identifier for virt devices as being used for qemu >> ARM64 ACPI support. >> >>

Hi, shutting down a Centos6 kvm guest does not work from outside doing a 'virsh shutdown vmguest', I've installed the CentOS-6.2-x86_64-minimal.iso inside the kvm guest I reckon this is related to acpi ... # dmesg | grep ACPI ACPI Error: A valid RSDP was not found (20090903/tbxfroot-219) ACPI: Interpreter disabled. pnp: PnP ACPI: disabled acpiphp: ACPI Hot Plug PCI Controller Driver

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > Added the match table and pointers for ACPI probing to the driver. > > This uses the same identifier for virt devices as being used for qemu > ARM64 ACPI support. > > http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e > > Signed-off-by: Graeme Gregory

On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: > On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > >> Added the match table and pointers for ACPI probing to the driver. > >> > >> This uses the same identifier for virt devices as being used for qemu

On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > Added the match table and pointers for ACPI probing to the driver. > > This uses the same identifier for virt devices as being used for qemu > ARM64 ACPI support. > > http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e > > Signed-off-by: Graeme Gregory

Hi, Given these C instructions: ============================== struct stru { struct stru *Next; }; struct list *NewStru = malloc ( sizeof ( struct stru ) ); struct list *tmp.3; ... tmp.3 = NewStru->Next; ============================== LLVM generates something like this: %tmp.0 = malloc %struct.stru ; <%struct.stru*> %tmp.3 = getelementptr %struct.stru* %tmp.0, int 0, uint 1 ;

On 28 July 2015 at 21:12, Peter Maydell <peter.maydell at linaro.org> wrote: > On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: >> On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >>> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >>> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme

Hi Misha, Thanks for your answer I was doing this: ======================== BasicBlock *BBlock = new BasicBlock("entry", MyFunc); ... Value *Zero = ConstantSInt::get(Type::IntTy, 0); Value *UZero = ConstantUInt::get(Type::UIntTy, 0); MallocInst* mi = new MallocInst( STyStru ); mi->setName("tmp.0"); BBlock->getInstList().push_back( mi );

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.