Re: [PATCH v3 04/21] vhost-vdpa: Use iommu_paging_domain_alloc()
On Mon, Jun 10, 2024 at 04:55:38PM +0800, Lu Baolu wrote:
> Replace iommu_domain_alloc() with iommu_paging_domain_alloc().
>
> Signed-off-by: Lu Baolu
Acked-by: Michael S. Tsirkin
I assume it's merged with the rest of the stuff, right?
> ---
> drivers/vhost/vdpa.c | 14 ++
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
> index 63a53680a85c..e31ec9ebc4ce 100644
> --- a/drivers/vhost/vdpa.c
> +++ b/drivers/vhost/vdpa.c
> @@ -1312,26 +1312,24 @@ static int vhost_vdpa_alloc_domain(struct vhost_vdpa
> *v)
> struct vdpa_device *vdpa = v->vdpa;
> const struct vdpa_config_ops *ops = vdpa->config;
> struct device *dma_dev = vdpa_get_dma_dev(vdpa);
> - const struct bus_type *bus;
> int ret;
>
> /* Device want to do DMA by itself */
> if (ops->set_map || ops->dma_map)
> return 0;
>
> - bus = dma_dev->bus;
> - if (!bus)
> - return -EFAULT;
> -
> if (!device_iommu_capable(dma_dev, IOMMU_CAP_CACHE_COHERENCY)) {
> dev_warn_once(&v->dev,
> "Failed to allocate domain, device is not IOMMU
> cache coherent capable\n");
> return -ENOTSUPP;
> }
>
> - v->domain = iommu_domain_alloc(bus);
> - if (!v->domain)
> - return -EIO;
> + v->domain = iommu_paging_domain_alloc(dma_dev);
> + if (IS_ERR(v->domain)) {
> + ret = PTR_ERR(v->domain);
> + v->domain = NULL;
> + return ret;
> + }
>
> ret = iommu_attach_device(v->domain, dma_dev);
> if (ret)
> --
> 2.34.1
Re: pull-request: ath-next-20240702
Jeff Johnson writes: > On 7/3/2024 12:14 AM, Kalle Valo wrote: >> Kalle Valo writes: >>> I see a weird warning from gpg which I have never seen before: >>> >>> merged tag 'ath-next-20240702' >>> gpg: Signature made Tue 02 Jul 2024 05:55:42 PM EEST >>> gpg:using EDDSA key 3F9AD487CCF522D7A21F0C492C15BBA0898CCB7B >>> gpg:issuer "jjohn...@kernel.org" >>> gpg: Good signature from "Jeff Johnson " [full] >>> gpg: WARNING: We do NOT trust this key! >>> gpg: The signature is probably a FORGERY. >>> >>> It first says that the signature is good and then claims it's a forgery, >>> odd. Is this a problem between using different email addresses or what? >> >> I did 'gpg --refresh-keys', now your key contains your kernel.org >> address and I don't see the warning anymore. >> > > There had to be at least one issue with my first PR. Glad you sorted it out. > Key management is still a mystery to me... This wasn't a problem in your pull request, It was just a problem between my chair and my display ;) But I have to say that I hate PGP, "user friendly" is clearly not part of their vocabulary. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Re: pull-request: ath-next-20240702
On 7/3/2024 12:14 AM, Kalle Valo wrote: > Kalle Valo writes: >> I see a weird warning from gpg which I have never seen before: >> >> merged tag 'ath-next-20240702' >> gpg: Signature made Tue 02 Jul 2024 05:55:42 PM EEST >> gpg:using EDDSA key 3F9AD487CCF522D7A21F0C492C15BBA0898CCB7B >> gpg:issuer "jjohn...@kernel.org" >> gpg: Good signature from "Jeff Johnson " [full] >> gpg: WARNING: We do NOT trust this key! >> gpg: The signature is probably a FORGERY. >> >> It first says that the signature is good and then claims it's a forgery, >> odd. Is this a problem between using different email addresses or what? > > I did 'gpg --refresh-keys', now your key contains your kernel.org > address and I don't see the warning anymore. > There had to be at least one issue with my first PR. Glad you sorted it out. Key management is still a mystery to me... /jeff
Re: pull-request: ath-next-20240702
Jeff Johnson wrote: > The following changes since commit bb678f01804ccaa861b012b2b9426d69673d8a84: > > Merge branch 'intel-wired-lan-driver-updates-2024-06-03' (2024-06-10 > 19:52:50 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git > tags/ath-next-20240702 > > for you to fetch changes up to 5344fc76f8944249026884157f846f88489edfc0: > > wifi: ath12k: Support TQM stats (2024-07-01 21:57:28 +0300) > > > ath.git patches for v6.11 > > We have moved to a new group-managed repo, and this is the first pull > request from that repo, and from me. Fingers crossed... > > We have some new features in ath12k along with some cleanups in ath11k > and ath12k. Also notable are some device-tree changes to allow certain > ath11k and ath12k devices to work with a new power sequencing > subsystem. > > Major changes: > > ath12k > > * DebugFS support for datapath statistics > * WCN7850: support for WoW (Wake on WLAN) > * WCN7850: device-tree bindings > > ath11k > > * QCA6390: device-tree bindings > > > Aaradhana Sahu (3): > wifi: ath12k: Fix WARN_ON during firmware crash in split-phy > wifi: ath12k: fix NULL pointer access in ath12k_mac_op_get_survey() > wifi: ath12k: fix uninitialize symbol error on ath12k_peer_assoc_h_he() > > Aditya Kumar Singh (3): > wifi: ath12k: fix per pdev debugfs registration > wifi: ath12k: unregister per pdev debugfs > wifi: ath12k: handle symlink cleanup for per pdev debugfs dentry > > Ajith C (1): > wifi: ath12k: fix firmware crash due to invalid peer nss > > Baochen Qiang (11): > wifi: ath12k: fix ACPI warning when resume > wifi: ath11k: fix RCU documentation in ath11k_mac_op_ipv6_changed() > wifi: ath11k: fix wrong handling of CCMP256 and GCMP ciphers > wifi: ath12k: add ATH12K_DBG_WOW log level > wifi: ath12k: implement WoW enable and wakeup commands > wifi: ath12k: add basic WoW functionalities > wifi: ath12k: add WoW net-detect functionality > wifi: ath12k: implement hardware data filter > wifi: ath12k: support ARP and NS offload > wifi: ath12k: support GTK rekey offload > wifi: ath12k: handle keepalive during WoWLAN suspend and resume > > Bartosz Golaszewski (2): > dt-bindings: net: wireless: qcom,ath11k: describe the ath11k on QCA6390 > dt-bindings: net: wireless: describe the ath12k PCI module > > Dinesh Karthikeyan (6): > wifi: ath12k: Add support to enable debugfs_htt_stats > wifi: ath12k: Add htt_stats_dump file ops support > wifi: ath12k: Add support to parse requested stats_type > wifi: ath12k: Support Transmit Scheduler stats > wifi: ath12k: Support pdev error stats > wifi: ath12k: Support TQM stats > > Harshitha Prem (1): > wifi: ath12k: Remove unused ath12k_base from ath12k_hw > > Karthikeyan Periyasamy (3): > wifi: ath12k: avoid unnecessary MSDU drop in the Rx error process > wifi: ath12k: fix mbssid max interface advertisement > wifi: ath12k: fix peer metadata parsing > > Lingbo Kong (3): > wifi: ath11k: fix ack signal strength calculation > wifi: ath11k: modify the calculation of the average signal strength in > station mode > wifi: ath12k: Fix pdev id sent to firmware for single phy devices > > Pradeep Kumar Chitrapu (1): > wifi: ath12k: fix legacy peer association due to missing HT or 6 GHz > capabilities > > Rameshkumar Sundaram (2): > wifi: ath12k: modify remain on channel for single wiphy > wifi: ath12k: fix driver initialization for WoW unsupported devices > > Ramya Gnanasekar (1): > wifi: ath12k: Dump additional Tx PDEV HTT stats > > Wolfram Sang (1): > wifi: ath11k: use 'time_left' variable with wait_event_timeout() > > .../bindings/net/wireless/qcom,ath11k-pci.yaml | 46 + > .../bindings/net/wireless/qcom,ath12k.yaml | 99 ++ > drivers/net/wireless/ath/ath11k/dp_rx.c|3 +- > drivers/net/wireless/ath/ath11k/dp_rx.h|3 + > drivers/net/wireless/ath/ath11k/dp_tx.c| 16 +- > drivers/net/wireless/ath/ath11k/dp_tx.h|4 +- > drivers/net/wireless/ath/ath11k/hal_tx.h |4 +- > drivers/net/wireless/ath/ath11k/mac.c | 29 +- > drivers/net/wireless/ath/ath11k/qmi.c | 20 +- > drivers/net/wireless/ath/ath12k/Makefile |3 +- > drivers/net/wireless/ath/ath12k/acpi.c |2 + > drivers/net/wireless/ath/ath12k/core.c | 71 +- > drivers/net/wireless/ath/ath12k/core.h | 34 +- > drivers/net/wireless/ath/ath12k/debug.h|3 +- > drivers/net/wireless/ath/ath12k/debugfs.c | 19 +- > drivers/net/wireless/ath/ath12k/debugfs.h |6 +- >
Re: pull-request: ath-next-20240702
Kalle Valo writes: > Jeff Johnson writes: > >> The following changes since commit bb678f01804ccaa861b012b2b9426d69673d8a84: >> >> Merge branch 'intel-wired-lan-driver-updates-2024-06-03' >> (2024-06-10 19:52:50 -0700) >> >> are available in the Git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git >> tags/ath-next-20240702 >> >> for you to fetch changes up to 5344fc76f8944249026884157f846f88489edfc0: >> >> wifi: ath12k: Support TQM stats (2024-07-01 21:57:28 +0300) >> >> >> ath.git patches for v6.11 >> >> We have moved to a new group-managed repo, and this is the first pull >> request from that repo, and from me. Fingers crossed... >> >> We have some new features in ath12k along with some cleanups in ath11k >> and ath12k. Also notable are some device-tree changes to allow certain >> ath11k and ath12k devices to work with a new power sequencing >> subsystem. >> >> Major changes: >> >> ath12k >> >> * DebugFS support for datapath statistics >> * WCN7850: support for WoW (Wake on WLAN) >> * WCN7850: device-tree bindings >> >> ath11k >> >> * QCA6390: device-tree bindings >> >> > > I see a weird warning from gpg which I have never seen before: > > merged tag 'ath-next-20240702' > gpg: Signature made Tue 02 Jul 2024 05:55:42 PM EEST > gpg:using EDDSA key 3F9AD487CCF522D7A21F0C492C15BBA0898CCB7B > gpg:issuer "jjohn...@kernel.org" > gpg: Good signature from "Jeff Johnson " [full] > gpg: WARNING: We do NOT trust this key! > gpg: The signature is probably a FORGERY. > > It first says that the signature is good and then claims it's a forgery, > odd. Is this a problem between using different email addresses or what? I did 'gpg --refresh-keys', now your key contains your kernel.org address and I don't see the warning anymore. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
[kvalo-ath:master] BUILD SUCCESS 26fe05a9c30960422e1d62d924c6eb6344ead1ae
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git master branch HEAD: 26fe05a9c30960422e1d62d924c6eb6344ead1ae Add localversion-wireless-testing-ath elapsed time: 2160m configs tested: 112 configs skipped: 1 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alpha allnoconfig gcc-13.2.0 arc allnoconfig gcc-13.2.0 arc randconfig-001-20240703 gcc-13.2.0 arc randconfig-002-20240703 gcc-13.2.0 arm alldefconfig gcc-13.2.0 arm allnoconfig gcc-13.2.0 arm davinci_all_defconfig gcc-13.2.0 arm gemini_defconfig gcc-13.2.0 armmulti_v5_defconfig gcc-13.2.0 arm randconfig-001-20240703 gcc-13.2.0 arm randconfig-002-20240703 gcc-13.2.0 arm randconfig-003-20240703 gcc-13.2.0 arm randconfig-004-20240703 gcc-13.2.0 arm spear13xx_defconfig gcc-13.2.0 arm versatile_defconfig gcc-13.2.0 arm64 allnoconfig gcc-13.2.0 arm64 randconfig-001-20240703 gcc-13.2.0 arm64 randconfig-002-20240703 gcc-13.2.0 arm64 randconfig-003-20240703 gcc-13.2.0 arm64 randconfig-004-20240703 gcc-13.2.0 csky allnoconfig gcc-13.2.0 csky randconfig-001-20240703 gcc-13.2.0 csky randconfig-002-20240703 gcc-13.2.0 i386 buildonly-randconfig-001-20240702 gcc-13 i386 buildonly-randconfig-002-20240702 gcc-13 i386 buildonly-randconfig-003-20240702 gcc-13 i386 buildonly-randconfig-004-20240702 gcc-13 i386 buildonly-randconfig-005-20240702 gcc-13 i386 buildonly-randconfig-006-20240702 gcc-13 i386 randconfig-001-20240702 gcc-13 i386 randconfig-002-20240702 gcc-13 i386 randconfig-003-20240702 gcc-13 i386 randconfig-004-20240702 gcc-13 i386 randconfig-005-20240702 gcc-13 i386 randconfig-006-20240702 gcc-13 i386 randconfig-011-20240702 gcc-13 i386 randconfig-012-20240702 gcc-13 i386 randconfig-013-20240702 gcc-13 i386 randconfig-014-20240702 gcc-13 i386 randconfig-015-20240702 gcc-13 i386 randconfig-016-20240702 gcc-13 loongarch allnoconfig gcc-13.2.0 loongarch randconfig-001-20240703 gcc-13.2.0 loongarch randconfig-002-20240703 gcc-13.2.0 m68k allnoconfig gcc-13.2.0 m68k amcore_defconfig gcc-13.2.0 microblazeallnoconfig gcc-13.2.0 mips allnoconfig gcc-13.2.0 mips eyeq5_defconfig gcc-13.2.0 mips ip27_defconfig gcc-13.2.0 mips maltaaprp_defconfig gcc-13.2.0 nios2 allnoconfig gcc-13.2.0 nios2 randconfig-001-20240703 gcc-13.2.0 nios2 randconfig-002-20240703 gcc-13.2.0 openrisc allnoconfig gcc-13.2.0 openrisc or1klitex_defconfig gcc-13.2.0 pariscallnoconfig gcc-13.2.0 pariscrandconfig-001-20240703 gcc-13.2.0 pariscrandconfig-002-20240703 gcc-13.2.0 powerpc allnoconfig gcc-13.2.0 powerpc randconfig-001-20240703 gcc-13.2.0 powerpc randconfig-002-20240703 gcc-13.2.0 powerpc randconfig-003-20240703 gcc-13.2.0 powerpc tqm8560_defconfig gcc-13.2.0 powerpc64 randconfig-001-20240703 gcc-13.2.0 powerpc64 randconfig-002-20240703 gcc-13.2.0 powerpc64 randconfig-003-20240703 gcc-13.2.0 riscv allnoconfig gcc-13.2.0 riscv defconfig gcc-13.2.0 riscv randconfig-001-20240703 gcc-13.2.0 riscv randconfig-002-20240703 gcc-13.2.0 s390 allnoconfig gcc-13.2.0 s390 randconfig-001-20240703 gcc-13.2.0 s390 randconfig-002-20240703 gcc-13.2.0 shallnoconfig gcc-13.2.0 sh j2_defconfig gcc-13.2.0 shrandconfig-001-20240703 gcc-13.2.0 shrandconfig-002-20240703 gcc-13.2.0 sh rts7751r2dplus_defconfig gcc-13.2.0 sh sh2007_defconfig
Re: pull-request: ath-next-20240702
Jeff Johnson writes: > The following changes since commit bb678f01804ccaa861b012b2b9426d69673d8a84: > > Merge branch 'intel-wired-lan-driver-updates-2024-06-03' (2024-06-10 > 19:52:50 -0700) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git > tags/ath-next-20240702 > > for you to fetch changes up to 5344fc76f8944249026884157f846f88489edfc0: > > wifi: ath12k: Support TQM stats (2024-07-01 21:57:28 +0300) > > > ath.git patches for v6.11 > > We have moved to a new group-managed repo, and this is the first pull > request from that repo, and from me. Fingers crossed... > > We have some new features in ath12k along with some cleanups in ath11k > and ath12k. Also notable are some device-tree changes to allow certain > ath11k and ath12k devices to work with a new power sequencing > subsystem. > > Major changes: > > ath12k > > * DebugFS support for datapath statistics > * WCN7850: support for WoW (Wake on WLAN) > * WCN7850: device-tree bindings > > ath11k > > * QCA6390: device-tree bindings > > I see a weird warning from gpg which I have never seen before: merged tag 'ath-next-20240702' gpg: Signature made Tue 02 Jul 2024 05:55:42 PM EEST gpg:using EDDSA key 3F9AD487CCF522D7A21F0C492C15BBA0898CCB7B gpg:issuer "jjohn...@kernel.org" gpg: Good signature from "Jeff Johnson " [full] gpg: WARNING: We do NOT trust this key! gpg: The signature is probably a FORGERY. It first says that the signature is good and then claims it's a forgery, odd. Is this a problem between using different email addresses or what? -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
