All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Mrzyglod <daniel.t.mrzyglod@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v4 3/6] lib/intel_mmio: use igt_device_map_pci_bar_region for mmap if fd is known.
Date: Fri, 26 Apr 2019 06:40:31 +0100	[thread overview]
Message-ID: <155625723098.3869.5434947766903910774@skylake-alporthouse-com> (raw)
In-Reply-To: <20190425205822.8995-4-daniel.t.mrzyglod@intel.com>

Quoting Daniel Mrzyglod (2019-04-25 21:58:19)
>  void
> -intel_mmio_use_pci_bar(struct pci_device *pci_dev)
> +intel_mmio_use_pci_bar(struct pci_device *pci_dev, int fd)
>  {
>         uint32_t devid, gen;
>         int mmio_bar, mmio_size;
> @@ -135,14 +136,28 @@ intel_mmio_use_pci_bar(struct pci_device *pci_dev)
>         else
>                 mmio_size = 2*1024*1024;
>  
> -       error = pci_device_map_range (pci_dev,
> -                                     pci_dev->regions[mmio_bar].base_addr,
> -                                     mmio_size,
> -                                     PCI_DEV_MAP_FLAG_WRITABLE,
> -                                     &igt_global_mmio);
> +       /* It's for some legacy tools existing in tree that require
> +        * working without driver
> +        */
> +
> +       if (fd == -1) {
> +               error = pci_device_map_range(pci_dev,
> +                                            pci_dev->regions[mmio_bar].base_addr,
> +                                            mmio_size,
> +                                            PCI_DEV_MAP_FLAG_WRITABLE,
> +                                            &igt_global_mmio);
> +
> +               igt_fail_on_f(error != 0, "Couldn't map MMIO region\n");
> +       } else {
> +               /* This method is much more convenient when we have many
> +                * concurrent PCI devices
> +                */
> +               igt_global_mmio = igt_device_map_pci_bar_region(fd, mmio_bar,
> +                                                               mmio_size);
> +               igt_fail_on_f(mmio_data->igt_mmio == MAP_FAILED,
> +                             "Couldn't map MMIO region\n");

This makes no sense to me at all. We already have the pci_device we
want and the BAR we want to mmap, so why repeat ourselves?

If you didn't want that pci_dev, why are we passing around the wrong
one?
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-04-26  5:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 20:58 [igt-dev] [PATCH i-g-t v4 0/6] Remove global igt_global_mmio Daniel Mrzyglod
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 1/6] lib/igt_device: add igt_device_get_pci_addr by fd Daniel Mrzyglod
2019-04-26  5:37   ` Chris Wilson
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 2/6] lib/igt_device: add igt_device_map_pci_bar_region Daniel Mrzyglod
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 3/6] lib/intel_mmio: use igt_device_map_pci_bar_region for mmap if fd is known Daniel Mrzyglod
2019-04-26  5:40   ` Chris Wilson [this message]
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 4/6] lib/intel_mmio: add pointer for read/write register funtions Daniel Mrzyglod
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 5/6] lib/intel_mmio: remove igt_global_mmio and move it to mmio_data Daniel Mrzyglod
2019-04-25 20:58 ` [igt-dev] [PATCH i-g-t v4 6/6] lib/ioctl_wrappers: add fd to aperture_mmap Daniel Mrzyglod
2019-04-25 21:55 ` [igt-dev] ✓ Fi.CI.BAT: success for Remove global igt_global_mmio (rev4) Patchwork
2019-04-26  9:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=155625723098.3869.5434947766903910774@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.t.mrzyglod@intel.com \
    --cc=igt-dev@lists.freedesktop.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.