[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH V3 1/2] xen: Update dm_op.h from Xen public header


  • To: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 25 Jul 2023 09:49:51 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=dnV2Wz9VIuWc6O3b1FpCA0oPWzq8AyxfKwpDVwjvO08=; b=CPYKuu34QIteLKvGDNuZ5mZbiL6IILt1A1H8US+3kZwjBz20xdRCVoS0YBM/SQCI4uuxx0cj+ioHmONoLS3ophK3/3ixC2RE9i15RvSBe9roLsbXR/RvF9j02i5hIw0rjhpGbDdSVqOY/Duhk5p/cGzpt3rlbvn+WcyN7nVGVb2Pcs9L3MC59x/OBciTorxhvvlA9ym89NcRLXuy4HZS6EnShyrEsn1tCEdv/ZBVsZ2ErpEWc6sL/JBFlWvwJlckA29PsNuL6yIqrq3VsxtStWUvKzLdQihSyHG6+WL1Qz84Dv4bq6fJuy/phOigxbwJDYhsKPfJGIDInCseLftZzQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U6nwFXTYzhMNzMK3ma1RLmzC04E+/o2rz5wWzWi5ApQ1TErhpn6bCmg5cwSUIIrGpwoziUEslZvp3ph/V5dNmHO/UbhE6iJ+JM93rEGeErR6C3JJks1meLLl85UniWE3oCJcwgxCDO3nsVbBD+M/hnJEXiFbbdp0cvw+634WGMmMZrm3g6MbEhWsHFMLDyOKKFFmZifG/GMMF3BUWZ7PS0gVJ9rqbLKkdM7nfhPtX1V/HHorBGiikjdQvoMNKfGqEuaTHk7pjU3UWlaGXKkPCXFpvYasi54+GaibhCErUns8OQ1moqfcbhbtn+nRW9jNxwvuez6JT+sxrdEIQgp+4Q==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: Vincent Guittot <vincent.guittot@xxxxxxxxxx>, Alex Bennée <alex.bennee@xxxxxxxxxx>, stratos-dev@xxxxxxxxxxxxxxxxxxx, Erik Schilling <erik.schilling@xxxxxxxxxx>, Manos Pitsidianakis <manos.pitsidianakis@xxxxxxxxxx>, Mathieu Poirier <mathieu.poirier@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
  • Delivery-date: Tue, 25 Jul 2023 07:50:06 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 25.07.2023 09:42, Viresh Kumar wrote:
> On 25-07-23, 09:18, Jan Beulich wrote:
>> I question that use, btw, but it is not up to me to decide whether to
>> accept such a layering violation in Linux. dm-op is, as its name says,
>> for device models to use. Your intended use doesn't fall in that
>> category, aiui. Imo the present contents of dm_op.h in Linux is indeed
>> all a kernel is supposed to know about, unless it was to gain in-kernel
>> device models.
> 
> Is there any other way by which an interrupt can be raised for the
> guest VM ? I was only aware of this method and so implemented it like
> this.
> 
> I am open to suggestions on this.

Well. I don't know your requirements. Generally I would suggest using
event channels, not interrupts, when talking about injecting events
into guests. If it strictly needs to be an interrupt, then I guess a
non-dm-op means would need introducing if none already exists.

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.