From: Jan Kiszka <jan.kiszka@siemens.com>
To: gsomlo@gmail.com
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-kmod PATCH] Provide pci_enable_msix_exact() for kernels < 3.15
Date: Wed, 07 May 2014 08:29:19 +0200 [thread overview]
Message-ID: <5369D2BF.2050509@siemens.com> (raw)
In-Reply-To: <20140506183427.GI5644@ERROL.INI.CMU.EDU>
On 2014-05-06 20:35, gsomlo@gmail.com wrote:
> Signed-off-by: Gabriel Somlo <somlo@cmu.edu>
> ---
>
> Jan,
>
> After today's pull from kvm, I also need this to build against my
> Fedora 20 kernel (3.13.10-200.fc20.x86_64).
Which version did you pull? Neither next nor queue contain this change yet.
>
> Thanks,
> Gabriel
>
> x86/external-module-compat.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/x86/external-module-compat.h b/x86/external-module-compat.h
> index dde9463..e62486b 100644
> --- a/x86/external-module-compat.h
> +++ b/x86/external-module-compat.h
> @@ -1480,6 +1480,11 @@ static inline int __register_hotcpu_notifier(struct notifier_block *nb)
> {
> return 0;
> }
> +static inline int pci_enable_msix_exact(struct pci_dev *dev,
> + struct msix_entry *entries, int nvec)
> +{
> + return -ENOSYS;
> +}
First, this is not x86-specific, thus should go to
external-module-compat-comm.h. Second, pci_enable_msix_exact was
introduced with 3.14. And then I think we can (and should) provide the
original content of this wrapper once it is needed, not a stub.
Right now I'm seeing different build problems:
http://buildbot.kiszka.org/kvm-kmod/builders/4-latest-kvm/builds/1788/steps/3.11-x86-64/logs/stdio
Didn't look into details yet.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-05-07 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 18:35 [kvm-kmod PATCH] Provide pci_enable_msix_exact() for kernels < 3.15 gsomlo
2014-05-07 6:29 ` Jan Kiszka [this message]
2014-05-07 6:54 ` Paolo Bonzini
2014-05-07 13:19 ` Gabriel L. Somlo
2014-05-07 17:14 ` Paolo Bonzini
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=5369D2BF.2050509@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gsomlo@gmail.com \
--cc=kvm@vger.kernel.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.