All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Nadav Amit <namit@cs.technion.ac.il>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org,
	bsd@redhat.com, avi.kivity@gmail.com
Subject: Re: [Qemu-devel] [PATCH 1/2] target-i386: disable LINT0 after reset
Date: Wed, 16 Sep 2015 07:23:30 +0200	[thread overview]
Message-ID: <55F8FCD2.2000003@siemens.com> (raw)
In-Reply-To: <1442351982.23936.157.camel@redhat.com>

On 2015-09-15 23:19, Alex Williamson wrote:
> On Mon, 2015-04-13 at 02:32 +0300, Nadav Amit wrote:
>> Due to old Seabios bug, QEMU reenable LINT0 after reset. This bug is long gone
>> and therefore this hack is no longer needed.  Since it violates the
>> specifications, it is removed.
>>
>> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
>> ---
>>  hw/intc/apic_common.c | 9 ---------
>>  1 file changed, 9 deletions(-)
> 
> Please see bug: https://bugs.launchpad.net/qemu/+bug/1488363
> 
> Is this bug perhaps not as long gone as we thought, or is there
> something else going on here?  Thanks,

I would say, someone needs to check if the SeaBIOS line that is supposed
to enable LINT0 is actually executed on one of the broken systems and,
if not, why not.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	Nadav Amit <namit@cs.technion.ac.il>
Cc: pbonzini@redhat.com, bsd@redhat.com, qemu-devel@nongnu.org,
	kvm@vger.kernel.org, avi.kivity@gmail.com
Subject: Re: [Qemu-devel] [PATCH 1/2] target-i386: disable LINT0 after reset
Date: Wed, 16 Sep 2015 07:23:30 +0200	[thread overview]
Message-ID: <55F8FCD2.2000003@siemens.com> (raw)
In-Reply-To: <1442351982.23936.157.camel@redhat.com>

On 2015-09-15 23:19, Alex Williamson wrote:
> On Mon, 2015-04-13 at 02:32 +0300, Nadav Amit wrote:
>> Due to old Seabios bug, QEMU reenable LINT0 after reset. This bug is long gone
>> and therefore this hack is no longer needed.  Since it violates the
>> specifications, it is removed.
>>
>> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
>> ---
>>  hw/intc/apic_common.c | 9 ---------
>>  1 file changed, 9 deletions(-)
> 
> Please see bug: https://bugs.launchpad.net/qemu/+bug/1488363
> 
> Is this bug perhaps not as long gone as we thought, or is there
> something else going on here?  Thanks,

I would say, someone needs to check if the SeaBIOS line that is supposed
to enable LINT0 is actually executed on one of the broken systems and,
if not, why not.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2015-09-16  5:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 23:32 [Qemu-devel][PATCH 0/2] target-i386: disable LINT0 after reset and init Nadav Amit
2015-04-12 23:32 ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-12 23:32 ` [Qemu-devel][PATCH 1/2] target-i386: disable LINT0 after reset Nadav Amit
2015-04-12 23:32   ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-13 14:12   ` [Qemu-devel][PATCH " Paolo Bonzini
2015-04-13 14:12     ` [Qemu-devel] [PATCH " Paolo Bonzini
2015-09-15 21:19   ` Alex Williamson
2015-09-15 21:19     ` Alex Williamson
2015-09-16  5:23     ` Jan Kiszka [this message]
2015-09-16  5:23       ` Jan Kiszka
2015-09-16  6:22       ` Nadav Amit
2015-09-16  6:22         ` [Qemu-devel] " Nadav Amit
2015-09-16  6:47       ` Gerd Hoffmann
2015-09-16  6:47         ` Gerd Hoffmann
2015-09-16 12:52         ` Nadav Amit
2015-09-16 12:52           ` Nadav Amit
2015-04-12 23:32 ` [Qemu-devel][PATCH 2/2] target-i386: kvm: Disable KVM quirks Nadav Amit
2015-04-12 23:32   ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-13 14:13   ` [Qemu-devel][PATCH " Paolo Bonzini
2015-04-13 14:13     ` [Qemu-devel] [PATCH " Paolo Bonzini
2015-04-13 14:17     ` Nadav Amit
2015-04-13 14:17       ` Nadav Amit
2015-04-13 14:24       ` Paolo Bonzini
2015-04-13 14:24         ` Paolo Bonzini
2015-04-13 14:33         ` Nadav Amit
2015-04-13 14:33           ` Nadav Amit
2015-04-13 14:36           ` Paolo Bonzini
2015-04-13 14:36             ` Paolo Bonzini

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=55F8FCD2.2000003@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=alex.williamson@redhat.com \
    --cc=avi.kivity@gmail.com \
    --cc=bsd@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=namit@cs.technion.ac.il \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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.