From: Markus Armbruster <armbru@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: serial8250: too much work for irq4
Date: Wed, 18 Feb 2009 19:18:20 +0100 [thread overview]
Message-ID: <87prhfd2xf.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <18844.18978.782069.848765@mariner.uk.xensource.com> (Ian Jackson's message of "Wed\, 18 Feb 2009 17\:49\:22 +0000")
Ian Jackson <Ian.Jackson@eu.citrix.com> writes:
> Keir Fraser writes ("Re: [Xen-devel] serial8250: too much work for irq4"):
>> Perhaps we could add a qemu command-line option to force accurate uart
>> emulation w.r.t. programmed FIFO depth and baud rate? Then those who want
>> this more accurate but more expensive and slower behaviour can configure it.
>
> That would certainly be possible. Our hw/serial.c is very like
> upstream's, and the same issue will apply to (for example) KVM, so we
> should coordinate any such change with upstream. I would suggest we
> crosspost the patch to xen-devel and qemu-devel.
>
> Markus: are you sufficiently bothered about this that you'd like to
> supply a patch to change the behaviour in the way Keir suggests :-).
>
> Ian.
;)
I don't yet know. I need to try the other patch you mentioned, and see
how the that flies. Anyway, the proposed change should most probably be
routed through upstream QEMU.
next prev parent reply other threads:[~2009-02-18 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 13:35 serial8250: too much work for irq4 Markus Armbruster
2009-02-18 11:08 ` Ian Jackson
2009-02-18 12:13 ` Markus Armbruster
2009-02-18 15:36 ` Ian Jackson
2009-02-18 17:04 ` Markus Armbruster
2009-02-18 17:27 ` Keir Fraser
2009-02-18 17:49 ` Ian Jackson
2009-02-18 18:18 ` Markus Armbruster [this message]
2009-02-19 16:45 ` Markus Armbruster
2009-02-19 17:04 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2004-07-23 10:39 Meelis Roos
2004-03-11 16:21 Meelis Roos
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=87prhfd2xf.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--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 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.