public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problems with serial interrupts with IPMI 2.0 SoL
Date: Thu, 10 Dec 2009 21:55:50 -0200	[thread overview]
Message-ID: <20091210215550.7f092006@pedra> (raw)
In-Reply-To: <4B216C12.1020001@goop.org>

Em Thu, 10 Dec 2009 13:45:54 -0800
Jeremy Fitzhardinge <jeremy@goop.org> escreveu:

> Hi,
> 
> I'm using a system with an embedded IPMI 2.0 BMC which provides SoL 
> (Supermicro X8SIL-F).  This works fine under Linux (fully interrupt 
> driven), but fails for Xen as it appears to not be sending interrupts; 
> it works OK if I set the driver to polling mode.
> 
> I'm assuming the Xen is tickling some bug in the emulated 16550.  The 
> Linux driver has a couple of pieces of code to explicitly work around 
> bugs in the Intel AMT SoL implementation, but I don't think they're 
> coming into play here (because there are no Intel SoL PCI devices on 
> this system to trigger the NO_TXEN_TEST flag).
> 
> I'm wondering if you have any pointers or suggestions about more subtle 
> problems?

If you don't hit NO_TXEN_TEST flag, you'll be loosing interrupts, as the
emulation of 16550 is not perfect.

As far as I remember, interrupts take too long to happen with the emulated
16550, when comparing with a normal serial.

-- 

Cheers,
Mauro

      reply	other threads:[~2009-12-10 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 21:45 Problems with serial interrupts with IPMI 2.0 SoL Jeremy Fitzhardinge
2009-12-10 23:55 ` Mauro Carvalho Chehab [this message]

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=20091210215550.7f092006@pedra \
    --to=mchehab@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox