From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Luca Boccassi <bluca@debian.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Neil Horman <nhorman@tuxdriver.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v3] igb_uio: fail and log if kernel lock down is enabled
Date: Fri, 29 Jun 2018 10:35:51 +0100 [thread overview]
Message-ID: <aa74919f-6932-62c0-c1f7-cf491c3921d2@intel.com> (raw)
In-Reply-To: <CALwxeUvWKqbq1kSp8zOozH63Cj19XcvVsTQv0J+UTyR6JgJUqQ@mail.gmail.com>
On 6/29/2018 8:04 AM, David Marchand wrote:
> Hello Ferruh,
>
> On Wed, May 16, 2018 at 4:42 PM, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>> @@ -136,3 +132,22 @@ static bool pci_check_and_mask_intx(struct pci_dev *pdev)
>> #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 5, 0)
>> #define HAVE_PCI_MSI_MASK_IRQ 1
>> #endif
>> +
>> +#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 8, 0)
>> +#define HAVE_ALLOC_IRQ_VECTORS 1
>> +#endif
>> +
>> +static inline bool igbuio_kernel_is_locked_down(void)
>> +{
>> +#ifdef CONFIG_LOCK_DOWN_KERNEL
>> +#ifdef CONFIG_LOCK_DOWN_IN_EFI_SECURE_BOOT
>> + return kernel_is_locked_down(NULL);
>> +#elif CONFIG_EFI_SECURE_BOOT_LOCK_DOWN
>> + return kernel_is_locked_down();
>> +#else
>> + return false;
>> +#endif
>> +#else
>> + return false;
>> +#endif
>> +}
>
> Missing some defined() for the check on CONFIG_EFI_SECURE_BOOT_LOCK_DOWN.
> It causes a build error with ubuntu-16.04 hwe for aarch64.
>
> I can send a patch.
Hi David,
You are right, please send the patch if have bandwidth for it, thanks.
next prev parent reply other threads:[~2018-06-29 9:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 16:56 [dpdk-dev] [PATCH] " Ferruh Yigit
2018-05-15 17:47 ` Luca Boccassi
2018-05-16 9:45 ` Ferruh Yigit
2018-05-16 9:56 ` Luca Boccassi
2018-05-15 18:52 ` Stephen Hemminger
2018-05-16 9:53 ` Ferruh Yigit
2018-05-16 10:18 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-05-16 10:50 ` Luca Boccassi
2018-05-16 14:42 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-05-17 11:34 ` Neil Horman
2018-05-17 13:26 ` Ferruh Yigit
2018-05-17 18:16 ` Neil Horman
2018-06-27 14:39 ` Thomas Monjalon
2018-06-29 7:04 ` David Marchand
2018-06-29 9:35 ` Ferruh Yigit [this message]
2018-05-16 11:47 ` [dpdk-dev] [PATCH] " Neil Horman
2018-05-17 13:23 ` Ferruh Yigit
2018-05-17 14:39 ` Stephen Hemminger
2018-05-17 19:49 ` Neil Horman
2018-05-22 15:23 ` Ferruh Yigit
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=aa74919f-6932-62c0-c1f7-cf491c3921d2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=stephen@networkplumber.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 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).