From: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>
To: "Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Lukasz Laguna" <lukasz.laguna@intel.com>,
"Adam Miszczak" <adam.miszczak@linux.intel.com>,
"Jakub Kolakowski" <jakub1.kolakowski@intel.com>,
"K V P Satyanarayana" <satyanarayana.k.v.p@intel.com>,
"C V Narasimha" <narasimha.c.v@intel.com>
Subject: Re: [PATCH i-g-t 2/3] lib/xe/xe_mmio: Fix assertion logic in xe_mmio_vf_access_init
Date: Wed, 11 Sep 2024 16:50:08 +0200 [thread overview]
Message-ID: <8273c690-6371-44f9-ad0c-58021fad6062@linux.intel.com> (raw)
In-Reply-To: <20240909154845.gab7r5u7qv72lrxp@kamilkon-DESK.igk.intel.com>
Hi,
On 9/9/2024 5:48 PM, Kamil Konieczny wrote:
> Hi Marcin,
> On 2024-09-04 at 10:47:00 +0200, Marcin Bernatowicz wrote:
>> Ensure igt_mmio is not null before proceeding.
>>
>
> Please change order of patches in patchseries, first fixes
> then addition of new test(s). Or this can be changed at merge
> or I could merge patches 2/3 and 3/3 first?
Please ignore the test patch. We need just the fixes to be merged.
>
>> Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
>> Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
>> Cc: Lukasz Laguna <lukasz.laguna@intel.com>
>> Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
>> Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
>> Cc: K V P Satyanarayana <satyanarayana.k.v.p@intel.com>
>> Cc: C V Narasimha <narasimha.c.v@intel.com>
>> ---
>> lib/xe/xe_mmio.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/xe/xe_mmio.c b/lib/xe/xe_mmio.c
>> index 57526d7cb..3e42b2e1c 100644
>> --- a/lib/xe/xe_mmio.c
>> +++ b/lib/xe/xe_mmio.c
>> @@ -25,7 +25,7 @@ void xe_mmio_vf_access_init(int pf_fd, int vf_id, struct xe_mmio *mmio)
>>
>> intel_mmio_use_pci_bar(&mmio->intel_mmio, pci_dev);
>>
>> - igt_assert(!mmio->intel_mmio.igt_mmio);
>> + igt_assert(mmio->intel_mmio.igt_mmio);
>
> Good catch, there is also "bool safe" in that struct,
> it could help to document the meaning of this field.
I guess it has to do with
* @safe: use safe register access tables
description to intel_register_access_init
>
> LGTM
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
Thanks for review
Marcin
>>
>> mmio->fd = pf_fd;
>> mmio->intel_mmio.safe = false;
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2024-09-11 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 8:46 [PATCH i-g-t 0/3] Introduce VF MMIO register tests and xe_mmio fixes Marcin Bernatowicz
2024-09-04 8:46 ` [PATCH i-g-t 1/3] tests/intel/xe_sriov_mmio_regs: Add tests to verify registers on VFs Marcin Bernatowicz
2024-09-11 14:33 ` Bernatowicz, Marcin
2024-09-04 8:47 ` [PATCH i-g-t 2/3] lib/xe/xe_mmio: Fix assertion logic in xe_mmio_vf_access_init Marcin Bernatowicz
2024-09-09 15:48 ` Kamil Konieczny
2024-09-11 14:50 ` Bernatowicz, Marcin [this message]
2024-09-04 8:47 ` [PATCH i-g-t 3/3] lib/xe/xe_mmio: Remove redundant PCI system cleanup Marcin Bernatowicz
2024-09-09 15:52 ` Kamil Konieczny
2024-09-04 18:58 ` ✓ Fi.CI.BAT: success for Introduce VF MMIO register tests and xe_mmio fixes Patchwork
2024-09-04 18:58 ` ✓ CI.xeBAT: " Patchwork
2024-09-06 2:49 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-06 21:25 ` ✗ CI.xeFULL: " Patchwork
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=8273c690-6371-44f9-ad0c-58021fad6062@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=lukasz.laguna@intel.com \
--cc=narasimha.c.v@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
/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