All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Burns <lists.xensource.com@adslpipe.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: MMIO ioremap() error with PCI passthrough
Date: Wed, 02 Jul 2008 13:54:04 +0100	[thread overview]
Message-ID: <486B7A6C.2030304@adslpipe.co.uk> (raw)
In-Reply-To: <486B4BC4.601@adslpipe.co.uk>

On 02/07/2008 10:35, Andy Burns wrote:

> I connected the aerial to it, it found one mux 
> and has started populating the EPG, it should find several muxes (it's 
> fed from the same amplifier as my other machine/tv)

Turns out the aerial outlet in the study had been disconnected and it 
was only picking up stray signals, a quick trip into the attic and a bit 
of re-wiring and myth is firing on all cylinders under Xen.

All muxes tuned OK, and recording 3 concurrent programs from the single 
tuner (which results in about 2Mbytes of data being read from the tuner 
and written to disk) eats less than 10% CPU in domU and 0.5% in dom0, 
about 130 interrupts/sec from the tuner.

Fantastic! Thanks again for your help, looking forward to Xen3.3

  reply	other threads:[~2008-07-02 12:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  8:17 MMIO ioremap() error with PCI passthrough Andy Burns
2008-07-01  8:30 ` Keir Fraser
2008-07-01  8:58   ` Andy Burns
2008-07-01  9:45     ` Keir Fraser
2008-07-01 13:16       ` Andy Burns
2008-07-01 13:31         ` Keir Fraser
2008-07-01 15:44           ` Andy Burns
2008-07-01 16:42             ` Andy Burns
2008-07-01 17:15               ` Keir Fraser
2008-07-01 18:50                 ` Andy Burns
2008-07-01 19:24                   ` Andy Burns
2008-07-01 19:57                     ` Keir Fraser
2008-07-01 22:27                       ` Andy Burns
2008-07-02  9:35               ` Andy Burns
2008-07-02 12:54                 ` Andy Burns [this message]
2008-07-02 14:09                   ` Andy Burns
2008-07-01 17:10             ` Keir Fraser
2008-07-01 18:52           ` Jeremy Fitzhardinge
2008-07-01  9:09   ` Andy Burns

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=486B7A6C.2030304@adslpipe.co.uk \
    --to=lists.xensource.com@adslpipe.co.uk \
    --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.