All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] xen: move PIRQ EOI map fields to arch_domain
Date: Tue, 8 Apr 2014 14:16:48 +0200	[thread overview]
Message-ID: <5343E8B0.2020505@citrix.com> (raw)
In-Reply-To: <5343FAC302000078000069DC@nat28.tlf.novell.com>

On 08/04/14 13:33, Jan Beulich wrote:
>>>> On 08.04.14 at 12:33, <roger.pau@citrix.com> wrote:
>> @@ -354,7 +353,7 @@ ret_t do_physdev_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
>>          }
>>          mfn = page_to_mfn(page);
>>  
>> -        if ( cmpxchg(&v->domain->arch.pv_domain.pirq_eoi_map_mfn,
>> +        if ( cmpxchg(&v->domain->arch.pirq_eoi_map_mfn,
> 
> In order to get here you also need to modify hvm_physdev_op().

This is on top of Mukesh PVH Dom0 v8 series (as stated on the 
description), which has the following in hvm_physdev_op:

static long hvm_physdev_op(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
{
    switch ( cmd )
    {
    default:
        if ( !is_pvh_vcpu(current) || !is_hardware_domain(current->domain) )
            return -ENOSYS;
        /* fall through */
    case PHYSDEVOP_map_pirq:
    case PHYSDEVOP_unmap_pirq:
    case PHYSDEVOP_eoi:
    case PHYSDEVOP_irq_status_query:
    case PHYSDEVOP_get_free_pirq:
        return do_physdev_op(cmd, arg);
    }
}

Thus allowing PVH Dom0 to use any PHYSDEVOP_*

Roger.

  reply	other threads:[~2014-04-08 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 10:33 [PATCH] xen: move PIRQ EOI map fields to arch_domain Roger Pau Monne
2014-04-08 11:33 ` Jan Beulich
2014-04-08 12:16   ` Roger Pau Monné [this message]
2014-04-08 13:01     ` Jan Beulich
2014-04-08 13:58       ` Roger Pau Monné
2014-04-08 14:04         ` Jan Beulich

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=5343E8B0.2020505@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.