>>> On 13.09.18 at 07:56, <kevin.t...@intel.com> wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: Monday, September 10, 2018 9:59 PM >> >> For one it is quite pointless to iterate over all pIRQ-s the domain has >> when just one is being adjusted. Introduce hvm_migrate_pirq(). > > it's migrate_pirq being introduced here.
Well, yes and no: As a static function, it should have been named migrate_pirq() already before. The statement above is about this becoming an externally accessible function. I'll add "externally accessible" to the description. >> Additionally it is bogus to migrate the pIRQ to a vCPU different from >> the one the event is supposed to be posted to - if anything, it might be >> worth considering not to migrate the pIRQ at all in the posting case. >> >> Signed-off-by: Jan Beulich <jbeul...@suse.com> > > Reviewed-by: Kevin Tian <kevin.t...@intel.com> Thanks. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
