[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] ns16550.c's poll_port variable

  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Fri, 04 May 2012 09:25:38 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Fri, 04 May 2012 08:26:27 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac0pz3wPgv5LAnWG3UW82f8d46J5Gg==
  • Thread-topic: ns16550.c's poll_port variable

On 04/05/2012 09:18, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> Hi Keir,
> does this really need to be a per-CPU variable? Can't a timer run only
> once at a time on the entire system (the more that it gets re-armed only
> at the end of the poll function, whereas the variable is consumed at the
> start), and hence the variable can be a simple one? Or else, what
> subtlety am I overlooking?

We set up a timer per initialised uart. There can be more than one (although
granted it is rare).

 -- Keir

> Thanks, Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.