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

Re: [PATCH v3 5/8] libxenguest: deal with log-dirty op stats overflow


  • To: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 26 Apr 2022 16:24:35 +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=kSUemzqtohV91lkmhBaOzyt4zzjFEIQ8k/mkTXSWZcE=; b=M1/S0mdFTfzhkcKOjfHuOdkA5Zwf7jnNDK4ZTdMkYBMVCTb/nsiGyCFcmsMYqkBkg6JkunFRIlnULqOJepvIcK3v8KH6aruuKIq6Bhc///3TkTFKS/Q/EgM+XBV6qMhYRZVOGQDAV+cb22C+8TeqAkc5LytzaakpexQXEUNpBBtuMcXhEf1UCMtdSGmXBAhua6Hz6+/IfJqNHCCv/ynYoDHWUfoK0rYIyjx4Wx3p/pPth+eDqzNPXA49txHLHO6Xd2wfK5N7hDEVO9fCiPc7ztpUv+HU7F00dIe+g6behe8BtS4KU5Mnrg6qgtwYNXYjynHCdC03/DxN8Ho5Obrzrw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Vu9S39fVbpQmqo5ZOv3bMbo7KuNja0QE+aUVLcUUC//R3p7KwncE+MGMO3F1SgBPV1qlWPUsnMiv0UlN3hvATiB98TmmbTi0ABvK1Lt2giIdXLEfYrGfyDS7J44FcUxbGUBs3VocpsaMazhKC5cWLHaJs1+cQGKOzErbJRs8qSSMVcbgLwH1ffViyPvWs6nFMz9TE0788leRo4KFP7AbcUQfreIQDGK3yRz6/Dx/1oH3kWQi68VY0WtP5n4iOv8wI9tMXAxSl2lvOnnDsrXPlonviy8BLzqdjoMq5pPyCQMcaFsii4HQDqRKMm3LirzCLZelnXRmscAM/Wj1+fJRig==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: Wei Liu <wl@xxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 26 Apr 2022 14:24:47 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 26.04.2022 12:54, Andrew Cooper wrote:
> On 26/04/2022 11:24, Jan Beulich wrote:
>> In send_memory_live() the precise value the dirty_count struct field
>> gets initialized to doesn't matter much
> 
> Yes it does.
> 
> And as you keep on refusing to actually fix the bugs pointed out during
> review, this entire series is NACKED, seeing as you've also repeatedly
> failed to address feedback from previous revisions on other patches.

Excuse me? Afair I did respond back, requesting further input from you.
It is this input which hasn't come forward; I don't see how I could
have made changes when I don't know what exactly I need to do. This is
emphasized by Ian giving a provisional ack on 'libxenguest: short-
circuit "all-dirty" handling', depending on you not proving him,
Jürgen (who had reviewed what is now the first two patches), and me
wrong. There again was no response from you. In such a case no
response can only mean "what I've heard back was satisfactory".

Also may I remind you that you're not in the position to NACK this
entire series. You can latch '"open" objections', yes, but it is at
best unfair to record objections without then working towards
resolving them, by simply remaining silent towards the request for
further input. This looks to be a repeating pattern, which is rather
frustrating. I fully recognize that in many areas you know things
better than I do, but this doesn't mean you're always right and I'm
always wrong. Therefore, like e.g. for patch 1 in this series, you
will want to actively convince the three people who think the change
is okay, rather than simply saying "no" with apparently none of the
three understanding why you say so.

I also view it as at least questionable behavior to NACK an entire
series when there are clearly issues which want taking care of. If
not by the patches in their present shape, then by whatever is
suitable (working out of which is why discussion needs to continue
until clarity is actually reached).

Jan




 


Rackspace

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