On Thu, Jun 14, 2012 at 06:11:18PM +0200, Jan Kiszka wrote:
> On 2012-06-14 18:05, Michael S. Tsirkin wrote:
> > On Thu, Jun 14, 2012 at 05:55:18PM +0200, Jan Kiszka wrote:
> >> On 2012-06-14 17:49, Michael S. Tsirkin wrote:
> >>> On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> >
On Thu, Jun 14, 2012 at 10:10:40AM -0600, Alex Williamson wrote:
> On Thu, 2012-06-14 at 19:05 +0300, Michael S. Tsirkin wrote:
> > On Thu, Jun 14, 2012 at 05:55:18PM +0200, Jan Kiszka wrote:
> > > On 2012-06-14 17:49, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex
On 2012-06-14 18:05, Michael S. Tsirkin wrote:
> On Thu, Jun 14, 2012 at 05:55:18PM +0200, Jan Kiszka wrote:
>> On 2012-06-14 17:49, Michael S. Tsirkin wrote:
>>> On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
msi_init() takes over a BAR without really specifying or allowing
On Thu, 2012-06-14 at 19:05 +0300, Michael S. Tsirkin wrote:
> On Thu, Jun 14, 2012 at 05:55:18PM +0200, Jan Kiszka wrote:
> > On 2012-06-14 17:49, Michael S. Tsirkin wrote:
> > > On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> > >> msi_init() takes over a BAR without really spec
On Thu, Jun 14, 2012 at 05:55:18PM +0200, Jan Kiszka wrote:
> On 2012-06-14 17:49, Michael S. Tsirkin wrote:
> > On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> >> msi_init() takes over a BAR without really specifying or allowing
> >> specification of how it does so. Instead, le
On 2012-06-14 17:49, Michael S. Tsirkin wrote:
> On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
>> msi_init() takes over a BAR without really specifying or allowing
>> specification of how it does so. Instead, let's split it into
>> two interfaces, one fully specified, and one tr
On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> msi_init() takes over a BAR without really specifying or allowing
> specification of how it does so. Instead, let's split it into
> two interfaces, one fully specified, and one trivially easy. This
> implements the latter. msix_i
On Thu, 2012-06-14 at 13:29 +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> > msi_init() takes over a BAR without really specifying or allowing
> > specification of how it does so. Instead, let's split it into
> > two interfaces, one fully spec
On Wed, Jun 13, 2012 at 10:51:19PM -0600, Alex Williamson wrote:
> msi_init() takes over a BAR without really specifying or allowing
> specification of how it does so. Instead, let's split it into
> two interfaces, one fully specified, and one trivially easy. This
> implements the latter. msix_i
msi_init() takes over a BAR without really specifying or allowing
specification of how it does so. Instead, let's split it into
two interfaces, one fully specified, and one trivially easy. This
implements the latter. msix_init_exclusive_bar() takes over
allocating and filling a PCI BAR _exclusiv
10 matches
Mail list logo
