xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Thu, 14 Oct 2010 09:57:09 -0400	[thread overview]
Message-ID: <20101014135709.GA2727@dumpdata.com> (raw)
In-Reply-To: <AANLkTikj1WrA18Y7VFf8utBDMeKz4+nz8Cxxz0bmfGe8@mail.gmail.com>

> >> You can't use SG buffers? And chain them together and provide them
> >> to the device? A lot of other drivers do this ...
> >
> > Perhaps. I don't know. I'm not the driver author. I think that it
> > worked using 1 giant buffer before so there was no need to use SG
> > buffers.
> 
> Got some more info. It's a hardware requirement for the tachyon chip.
> It uses a 2 MB block for the FC SEST index table. It's one place where
> we can't use SG.

OK, pci_alloc_consistent is the way. I think you can go up to 2MB with it.

> It really not a matter of laziness.

<nods>

  reply	other threads:[~2010-10-14 13:57 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` Konrad Rzeszutek Wilk
2010-09-27 19:16   ` Bruce Edge
2010-09-27 19:54     ` Konrad Rzeszutek Wilk
2010-09-27 23:54       ` Bruce Edge
2010-09-28  1:15         ` Jiang, Yunhong
2010-09-28  3:16           ` Bruce Edge
2010-09-28  3:26             ` Jiang, Yunhong
2010-09-28  4:45               ` Bruce Edge
2010-09-28 16:08                 ` Lin, Ray
2010-09-28 16:19                   ` Konrad Rzeszutek Wilk
2010-09-28 18:35                     ` Lin, Ray
2010-09-28 20:14                       ` Konrad Rzeszutek Wilk
2010-09-28 20:38                         ` Lin, Ray
2010-09-29  0:53                     ` Jiang, Yunhong
2010-09-30 16:30                       ` Lin, Ray
2010-09-28 14:56         ` Konrad Rzeszutek Wilk
2010-09-30 18:55           ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19   ` Bruce Edge
2010-10-01 23:30   ` Bruce Edge
2010-10-03  5:46     ` Bruce Edge
2010-10-03 12:08       ` Pasi Kärkkäinen
2010-10-04 14:48     ` Konrad Rzeszutek Wilk
2010-10-05 18:21       ` Bruce Edge
2010-10-06 14:21         ` Konrad Rzeszutek Wilk
2010-10-06 18:21           ` Bruce Edge
2010-10-08 16:48             ` Lin, Ray
2010-10-08 17:30               ` Konrad Rzeszutek Wilk
2010-10-08 17:40                 ` Lin, Ray
2010-10-08 17:52                 ` Bruce Edge
2010-10-08 21:01                   ` Lin, Ray
2010-10-08 17:56   ` Bruce Edge
2010-10-11 21:12   ` Bruce Edge
2010-10-11 21:46     ` Konrad Rzeszutek Wilk
2010-10-13 21:36       ` Bruce Edge
2010-10-13 21:46         ` Konrad Rzeszutek Wilk
2010-10-13 22:00           ` Bruce Edge
2010-10-13 22:08             ` Bruce Edge
2010-10-14 13:57               ` Konrad Rzeszutek Wilk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` Konrad Rzeszutek Wilk

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=20101014135709.GA2727@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=bruce.edge@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).