From nobody Wed Oct 19 17:39:19 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MsyfG3ZSsz4gVTW for ; Wed, 19 Oct 2022 17:39:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MsyfF1hjcz3pmN for ; Wed, 19 Oct 2022 17:39:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ej1-x62f.google.com with SMTP id ot12so41785299ejb.1 for ; Wed, 19 Oct 2022 10:39:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8lsUOQu9ZgSf+8JPAH408M0rKcnPxhQ3SUznBTf7+3A=; b=OBOW6qAD4HM2RQ4xsMdSDnEfC/lub9CCmJcMo8el8DKMbd64BpF29xbAjE4es2zQ3R yzn/P89xtO9Sp4Z6NGIzyJH0XmKrGChuo8eRGhoeBaRoJF/4gmv6i5t79+1mRP9P5TOR x/g34c7lPPcBKwZezgmXLCukvSOEuBvM46hlz6QGZidUz8qY/RHWpApZ8WHiK4eAJrOC W+DPRPFwQ8vLw/2YuUU/Z7GO7s4BHlx7OHoSAAewl0bH/QGiv3h+UMX2JAt9rhdZpCxt s14Axvxqpmj63EHHsOd6W5RyJJqKWWVocUuUBY6wpxBYAZj3se2muQmNWlxSFM2blK5R 4ytg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8lsUOQu9ZgSf+8JPAH408M0rKcnPxhQ3SUznBTf7+3A=; b=NgqrJp/qGBfUhL+LSRmTne4RXSfxfgOq4a22EGkuXC8R9bMbLr1DL+EKmmh3zX1eCS 7tDZVLMLGus1+8kpUNgrBZTPb3dM309ZqwD3PM3VGy3a1IMhVkSNWH0gu656U7i87bXl lkelKZt7NlLO2aQS/IurVB+jcD43M8cb2Bp+wD4R7CMSPuFMRnV0/A3PGVfFvAZQ/HVc wSQ71RpeYsmLTiq2FBafQviFBOCpnLGHWFPt7gHyE1iL9S7ZndW41zo7piHouXHZqZBW Meixcdqzuie5XY4Sc+nqzVT0AMzK/6RleVMOf36kpjoqHBnegKwqzRNDQKUfki5BC46d RhKQ== X-Gm-Message-State: ACrzQf2BRu7WKkSH3woClpUIJ51N10b/bwlv+FDDBDl2k31fVeHuAMey LhXxToJbHQ1L6KKiqQ37fNna9+GsdjjLeEWfQ9lEVg== X-Google-Smtp-Source: AMsMyM4UzpzQ3xF9wYydwPV13ySx2TaquSZnaM8WwXlrEDHzTtQlvVKTosBHdxE56E5oqVzJI2VCkgh6QcJ25QOB+Uk= X-Received: by 2002:a17:907:16a7:b0:78d:f586:e446 with SMTP id hc39-20020a17090716a700b0078df586e446mr7759671ejc.252.1666201171161; Wed, 19 Oct 2022 10:39:31 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Wed, 19 Oct 2022 11:39:19 -0600 Message-ID: Subject: Re: allocating IRQ mentioned in _CRS of ACPI To: Souradeep Chakrabarti Cc: "freebsd-hackers@freebsd.org" , Wei Hu Content-Type: multipart/alternative; boundary="000000000000ee990a05eb66b0a4" X-Rspamd-Queue-Id: 4MsyfF1hjcz3pmN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=OBOW6qAD; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2a00:1450:4864:20::62f) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62f:from]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_TLS_LAST(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; RCPT_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000ee990a05eb66b0a4 Content-Type: text/plain; charset="UTF-8" Sorry for the late reply... I've been busy with some things for work... I think you'll need to get the parent of vmbus to allow a pass through allocation. What bus is that currently? Warner On Tue, Oct 18, 2022 at 12:33 PM Souradeep Chakrabarti < schakrabarti@microsoft.com> wrote: > Hi, > It will be a great help, if someone can help here with some idea. > As it is blocking the FreeBSD on Hyper-V ARM64. > > Thanks & Regards, > Souradeep > > > -----Original Message----- > > From: Souradeep Chakrabarti > > Sent: Friday, October 14, 2022 1:24 PM > > To: 'Warner Losh' > > Cc: freebsd-hackers@freebsd.org; Wei Hu > > Subject: RE: allocating IRQ mentioned in _CRS of ACPI > > > > Last mail was having incorrect FreeBSD hacker alias. Replacing that with > correct > > one here. > > > > > > > -----Original Message----- > > > From: Souradeep Chakrabarti > > > Sent: Friday, October 14, 2022 1:19 PM > > > To: Warner Losh > > > Cc: hacker@freebsd.org; Wei Hu > > > Subject: allocating IRQ mentioned in _CRS of ACPI > > > > > > Hi, > > > I would like to allocate IRQ to a device, mentioned in the _CRS of > > > that device in ACPI table. > > > I have tried with bus_alloc_resource_any(), but it is failing as the > > > parent of that device is not owning the IRQ. > > > > > > Current ACPI topo for the device : > > > ACPI0->SB.VMOD(HID ACPI0004, has SYS_RES_MEM for MMIO in _CRS)- > > > >VMBUS( it has SYS_RES_IRQ in it's _CRS). > > > > > > How can I get here both SYS_RES_IRQ and SYS_RES_MEM allocated to VMBUS? > > > > > > Thanks & Regards, > > > Souradeep > --000000000000ee990a05eb66b0a4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for the=C2=A0late reply... I've been busy w= ith some things for work...

I think you'll nee= d to get the parent of vmbus to allow a pass through allocation. What bus i= s that
currently?

Warner

On Tue, Oct = 18, 2022 at 12:33 PM Souradeep Chakrabarti <schakrabarti@microsoft.com> wrote:
Hi,
It will be a great help, if someone can help here with some idea.
As it is blocking the FreeBSD on Hyper-V ARM64.

Thanks & Regards,
Souradeep

> -----Original Message-----
> From: Souradeep Chakrabarti
> Sent: Friday, October 14, 2022 1:24 PM
> To: 'Warner Losh' <imp@bsdimp.com>
> Cc: f= reebsd-hackers@freebsd.org; Wei Hu <weh@microsoft.com>
> Subject: RE: allocating IRQ mentioned in _CRS of ACPI
>
> Last mail was having incorrect FreeBSD hacker alias. Replacing that wi= th correct
> one here.
>
>
> > -----Original Message-----
> > From: Souradeep Chakrabarti
> > Sent: Friday, October 14, 2022 1:19 PM
> > To: Warner Losh <imp@bsdimp.com>
> > Cc: hacke= r@freebsd.org; Wei Hu <weh@microsoft.com>
> > Subject: allocating IRQ mentioned in _CRS of ACPI
> >
> > Hi,
> > I would like to allocate IRQ to a device, mentioned in the _CRS o= f
> > that device in ACPI table.
> > I have tried with bus_alloc_resource_any(), but it is failing as = the
> > parent of that device is not owning the IRQ.
> >
> > Current ACPI topo for the device :
> > ACPI0->SB.VMOD(HID ACPI0004, has SYS_RES_MEM for MMIO in _CRS)= -
> > >VMBUS( it has SYS_RES_IRQ in it's _CRS).
> >
> > How can I get here both SYS_RES_IRQ and SYS_RES_MEM allocated to = VMBUS?
> >
> > Thanks & Regards,
> > Souradeep
--000000000000ee990a05eb66b0a4--